Data storage system

ABSTRACT

A data storage system includes multiple head nodes and data storage sleds. A control plane of the data storage system designates, for a volume partition, one of the head nodes to function as a primary head node storing a primary replica of the volume partition and designates two or more other head nodes to function as reserve head nodes storing reserve replicas of the volume partition. Additionally, the primary head node causes volume data for the volume partition to be erasure encoded and stored on multiple mass storage devices in different ones of the data storage sleds.

PRIORITY INFORMATION

This application is a continuation-in-part of U.S. application Ser. No. 15/392,857, entitled “Data Storage System with Multiple Durability Levels,” filed Dec. 28, 2016, which is hereby incorporated by reference in its entirety.

BACKGROUND

The recent revolution in technologies for dynamically sharing virtualizations of hardware resources, software, and information storage across networks has increased the reliability, scalability, and cost efficiency of computing. More specifically, the ability to provide on demand virtual computing resources and storage through the advent of virtualization has enabled consumers of processing resources and storage to flexibly structure their computing and storage costs in response to immediately perceived computing and storage needs. Virtualization allows customers to purchase processor cycles and storage at the time of demand, rather than buying or leasing fixed hardware in provisioning cycles that are dictated by the delays and costs of manufacture and deployment of hardware. Rather than depending on the accuracy of predictions of future demand to determine the availability of computing and storage, users are able to purchase the use of computing and storage resources on a relatively instantaneous as-needed basis.

Virtualized computing environments are frequently supported by block-based storage. Such block-based storage provides a storage system that is able to interact with various computing virtualizations through a series of standardized storage calls that render the block-based storage functionally agnostic to the structural and functional details of the volumes that it supports and the operating systems executing on the virtualizations to which it provides storage availability.

Some block-based storage systems utilize a server node and multiple storage nodes that are serviced by the server node or dual server nodes that service multiple storage nodes. For example, a storage area network (SAN) may include such an architecture. However, in such systems, a failure of one or more of the server nodes may result in a large amount of storage capacity served by the server node(s) being rendered unusable or may result in significant decreases in the ability of the storage system to service read and write requests.

In order to increase durability of data, some block-based storage systems may store data across multiple devices in multiple locations. For example, a SAN may span multiple locations such as different facilities or different geographic locations. Such systems may utilize a common control plane to manage data in the multiple locations. However, in such systems, a failure of a component of the common control plane may impact a large quantity of storage capacity and render the large quantity of storage capacity unavailable. Also, such systems may require extensive networks to move data between the multiple locations and may also result in high latencies for data recovery due to data being located across the multiple locations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a data storage unit comprising head nodes and data storage sleds, according to some embodiments.

FIG. 2 is a block diagram illustrating a provider network implementing multiple network-based services including a block-based storage service that includes data storage units, according to some embodiments.

FIG. 3A is a block diagram illustrating head nodes and data storage sleds of a data storage unit storing block storage data in response to a write request, according to some embodiments.

FIG. 3B is a block diagram illustrating head nodes of a data storage unit re-mirroring data to a replacement head node for a volume partition, according to some embodiments.

FIGS. 4A-4B are block diagrams illustrating a log storage and index of a head node storage, according to some embodiments.

FIG. 5 illustrates a partial view of a data storage unit that stores portions of a volume partition in multiple mass storage devices in multiple data storage sleds on multiple shelves of the data storage unit, according to some embodiments.

FIGS. 6A-B illustrate columns of mass storage devices storing different portions of a volume partition, according to some embodiments.

FIG. 7 is a high-level flowchart illustrating operations performed by a head node in response to a request to store data in a data storage unit, according to some embodiments.

FIG. 8A is a high-level flowchart illustrating a replacement head node being designated for a volume partition to replace a failed head node such that two or more reserve head nodes for the volume partition are maintained, according to some embodiments.

FIG. 8B is a high-level flowchart illustrating a replacement head node re-mirroring log data and volume index data from a surviving primary head node or surviving reserve head node, according to some embodiments.

FIG. 8C is a high-level flowchart illustrating a reserve head node enforcing an authorization for a replica for a volume partition, according to some embodiments.

FIG. 9 is a high-level flowchart illustrating a fast failover of a head node with low performance, according to some embodiments.

FIG. 10 is a block diagram illustrating a head node failure detection agent identifying a failed head node, according to some embodiments.

FIG. 11A is an example user interface to a block storage service, wherein a client can specify a durability for one or more of the client's volumes, according to some embodiments.

FIG. 11B is a high-level flowchart illustrating head node replication adjustments or erasure encoding adjustments being made to meet a client's durability requirement for a volume of the client, according to some embodiments.

FIG. 12A is a high-level flowchart illustrating operations performed by a head node in response to a failed mass storage device in a data storage sled of a data storage unit, according to some embodiments.

FIG. 12B is a high-level flowchart illustrating operations performed by a head node in response to a failed mass storage device in a data storage sled of a data storage unit, according to some embodiments.

FIG. 13A is a block diagram illustrating a process for creating a volume involving a zonal control plane, a local control plane, and head nodes of a data storage system, according to some embodiments.

FIG. 13B is a block diagram illustrating head nodes of a data storage unit servicing read and write requests independent of a zonal control plane of a data storage system, according to some embodiments.

FIG. 14A is a block diagram of a head node, according to some embodiments.

FIG. 14B is a block diagram of a data storage sled, according to some embodiments.

FIG. 15 is a high-level flowchart illustrating a process of creating a volume in a data storage system, according to some embodiments.

FIG. 16A is a high-level flowchart illustrating a local control plane of a data storage unit providing storage recommendations to a head node of the data storage unit for locations to store data in data storage sleds of the data storage unit for a volume serviced by the head node, according to some embodiments.

FIG. 16B is a high-level flowchart illustrating a head node of a data storage unit storing data in data storage sleds of the data storage unit, according to some embodiments.

FIG. 17 is a high-level flowchart illustrating head nodes of a data storage unit performing a fail over operation in response to a failure of or loss of communication with one of the head nodes of the data storage unit, according to some embodiments.

FIG. 18 is a block diagram illustrating performance and/or usage metrics being collected and accumulated in a data storage unit, according to some embodiments.

FIG. 19 illustrates interactions between a local control plane, head nodes, and data storage sleds of a data storage unit in relation to writing data to mass storage devices of a data storage sled of a data storage unit, according to some embodiments.

FIG. 20 is a high-level flowchart of a head node of a data storage unit flushing data stored in a storage of the head node to a data storage sled of the data storage unit, according to some embodiments.

FIG. 21 is a high-level flowchart of a sled controller of a data storage sled processing a write request, according to some embodiments.

FIGS. 22A-D illustrate a data storage unit with redundant network paths within the data storage unit, according to some embodiments.

FIGS. 23A-C illustrate a data storage unit configured to allow scaling of storage capacity and processing capacity, according to some embodiments.

FIG. 24 is a block diagram illustrating an example computing system, according to some embodiments.

While embodiments are described herein by way of example for several embodiments and illustrative drawings, those skilled in the art will recognize that the embodiments are not limited to the embodiments or drawings described. It should be understood, that the drawings and detailed description thereto are not intended to limit embodiments to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope as defined by the appended claims. The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word “may” is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including, but not limited to.

DETAILED DESCRIPTION

According to one embodiment, a data storage system includes a rack, a plurality of head nodes mounted in the rack, and a plurality of data storage sleds mounted in the rack. For a partition of a volume to be stored in the data storage system, a control plane of the data storage system designates a particular one of the head nodes as a primary head node for the volume partition and designates two or more other ones of the head nodes as reserve head nodes for the volume partition. In response to receiving a write request for the volume partition, the head node designated as the primary head node for the volume partition is configured to write data included with the write request to a storage of the head node designated as the primary head node and cause the data included with the write request to be replicated to the other head nodes designated as the reserve head nodes for the volume partition. Furthermore, the head node designated as the primary head node for the volume partition is further configured to cause respective parts of the data stored in the storage of the head node to be stored in a plurality of respective mass storage devices each in different ones of the plurality of data storage sleds of the data storage system.

For example, a data storage system may store data in a storage of a primary head node and replicate the data to respective storages of a two or more reserve head nodes (e.g. secondary head nodes). Then, after a certain amount of time has passed, a certain amount of data has been written for the volume partition, or in response to another trigger, the head node may cause the data stored in the storage of the primary head node to be stored in multiple mass storage devices of different ones of the data storage sleds of the data storage system. For example, data may be stored in mass storage devices of different data storage sleds of a data storage system in a RAID array and may be erasure encoded across the multiple mass storage devices. Such a system may provide varying latencies for accessing stored data and different durabilities of the stored data based on whether the data is stored in storages of the primary and reserve head nodes or stored in multiple mass storage devices of multiple data storage sleds of the data storage system. In some embodiments, durability of data stored and replicated in head nodes may be adjusted by varying a number of head nodes that replicate the data. Also, durability of data stored in mass storage devices of data storage sleds of a data storage system may be adjusted by varying a RAID scheme or data encoding procedure used to store the data amongst other techniques to increase data durability.

According to one embodiment, a data storage system includes a head node of a data storage system. The head node, when acting as a primary head node of the data storage system for the volume partition and in response to receiving a write request for a volume partition, is configured to write data included with the write request to a storage of the head node and cause the data included with the write request to be replicated to two or more other head nodes of the data storage system acting as reserve head nodes for the volume partition. The head node is further configured to cause respective parts of the data stored in the storage of the head node to be stored in a plurality of respective mass storage devices each in different ones of the plurality of data storage sleds mounted in the rack of the data storage system.

According to one embodiment, a method includes receiving a write request for a volume partition, by a head node of a data storage system acting as a primary head node for the volume partition. The method further includes the head node writing data included in the write request to a storage of the head node and causing the data included with the write request to be replicated from the head node to a set of two or more other head nodes of the data storage system acting as reserve head nodes for the volume partition. Additionally, the method includes the head node receiving additional write requests for the volume partition and performing, for the additional write requests, said writing data included in the additional write requests to the storage of the head node and said causing data included in the additional write requests to be replicated to the set of two or more head nodes. Also, the method includes, causing respective parts of the data included in the write request and the additional write requests that is stored in the storage of the head node to be erasure encoded and stored in a plurality of mass storage devices of the data storage system.

Some data storage systems, such as storage area networks (SAN) may allow a server or a pair of servers to access a shared set of storage resources. However, such systems may be susceptible to significant losses in performance due to a server failure. Also, in such systems, data may be durably stored in storage devices of the SAN network, but not durably stored in the servers accessing the SAN network.

In order to provide high durability data storage and low latencies for accessing data, a data storage unit may store data in local storages of head nodes that function as servers for the data storage system, replicate the data to other head nodes of the data storage unit, and also store the data across multiple mass storage devices in multiple data storage sleds of the data storage unit. Thus, a data storage system that includes a data storage unit may provide low latency input/output operations for data stored in a storage of a head node, while still providing data durability due to the data being replicated to other head nodes. Furthermore, the data storage system may provide equivalent or higher durability for the data once the data is stored in multiple mass storage devices in different data storage sleds of the data storage unit. Thus, a data storage system may provide high levels of data durability and low input/output operation latency for data stored in a storage of a head node and replicated to other head nodes and for data stored in multiple mass storage devices in different data storage sleds of the data storage system.

In some embodiments, data may be initially stored in a storage of a head node and replicated to a storage of two or more other head nodes, and may be asynchronously copied to multiple mass storage devices in different data storage sleds that form a RAID array (random array of independent disks) to store the data. In some embodiments, recently stored data or frequently accessed data may remain in a head node storage to allow for low latency access to the data. The data may then be copied to mass storage devices in data storage sleds of a data storage unit of the data storage system after a certain amount of time has elapsed since the data was last accessed or stored. Relocating the data to the mass storage devices may maintain or increase a durability of the data as compared to the data being stored in a storage of a primary head node and being replicated to a storage of two or more reserve head nodes. In some embodiments, other criteria may be used to determine when data stored in a storage of a head node is to be moved to mass storage devices of data storage sleds of a data storage unit. For example, data may be collected in a log of a head node and upon an amount of data being stored in the log exceeding a threshold amount, the data may be relocated to mass storage devices of data storage sleds of a data storage unit of the data storage system.

In some embodiments, a data storage unit of a data storage system may include multiple head nodes, multiple data storage sleds, and at least two networking devices. The data storage unit may further include connectors for coupling the data storage unit with at least two separate power sources. The data storage unit may also include at least two power distribution systems within the data storage unit to provide redundant power to the head nodes, the data storage sleds, and the networking devices of the data storage unit. Furthermore, the at least two networking devices of the data storage unit may implement at least two redundant networks within the data storage unit that enable communications between the head nodes of the data storage unit and the data storage sleds of the data storage unit. Furthermore, the at least two networking devices of the data storage unit may implement at least two redundant networks within the data storage unit that enable communications between the head nodes of the data storage unit and external clients of the data storage unit. In some embodiments, a data storage unit that includes redundant networks and redundant power may provide high reliability and data durability for data storage and access while storing data locally within devices mounted within a single rack.

In some embodiments, a data storage unit of a data storage system may include multiple head nodes that are assigned network addresses that are routable from devices external to the data storage unit. Thus, external clients may communicate directly with head nodes of a data storage unit without the communications being routed through a control plane of the data storage system that is external to the data storage unit, such as a zonal control plane. Also, a data storage system that includes multiple data storage units may implement a zonal control plane that assigns volumes or volume partitions to particular ones of the data storage units of the data storage system. Also, a zonal control plane may coordinate operations between data storage units, such as rebalancing loads by moving volumes between data storage units. However, a data storage unit may also implement a local control plane configured to perform fail over operations for head nodes and mass storage devices of data storage sleds of the data storage unit. Because head nodes of a data storage unit may communicate directly with client devices and because a local control plane may manage fail over operations within a data storage unit, the data storage unit may operate autonomously without relying on a zonal control plane once a volume has been created on the data storage unit.

In some embodiments, in order to prevent corruption of data stored in mass storage devices of a data storage system, a data control plane may be at least partially implemented on a sled controller of a data storage sled of the data storage system. The data storage sled may include multiple mass storage devices serviced by the sled controller. Also, portions of respective mass storage devices of a particular data storage sled may be reserved for a particular volume serviced by a particular head node functioning as a primary head node for the particular volume. In order to reserve the portions for the particular volume or a volume partition of the particular volume, a sled controller of a data storage sled may provide a token to a head node requesting to reserve the portions. Once the portions are reserved for the particular volume or volume partition by the head node acting as the primary head node, the head node while acting as a primary head node for the particular volume or volume partition, may provide the token to the sled controller along with a write request when writing new data to the portions. The sled controller may verify the token and determine the head node is authorized to write to the portions. Also, the sled controller may be configured to prevent writes from head nodes that are not authorized to write to the particular portions of the mass storage devices of the data storage sled that includes the sled controller. The sled controller may refuse to perform a write request based on being presented an invalid token or based on a token not being included with a write request.

In some embodiments, a control plane such as a local control plane or a zonal control plane of a data storage system may issue unique sequence numbers to head nodes of the data storage system to indicate which head node is a primary head node for a particular volume or volume partition. A primary head node may present a sequence number issued from a control plane to respective ones of the sled controllers of respective ones of the data storage sleds to reserve, for a particular volume or volume partition, respective portions of mass storage devices serviced by the respective ones of the respective sled controllers. In response, the sled controllers may issue a token to the primary head node to be included with future write requests directed to the respective portions.

In order to facilitate a failover operation between a primary head node and a reserve head node of a set of reserve head nodes, a control plane may issue new credentials, e.g. a new sequence number, to a set of head nodes that includes a reserve head node assuming a role of primary head node for a volume or volume partition. Additionally, once a replacement reserve head node has been designated for the volume partition, the control plane may issue another new credential, e.g. a new sequence number. In some embodiments, each time a membership change occurs for a set of head nodes that implement a primary head node and a set of two or more reserve head nodes for a volume partition, a control plane may issue a new sequence number to the head nodes included in the set with the changed membership. In some embodiments, the newly issued sequence number may be used to perform a failover and to ensure writes replicated between the head nodes and written to the data storage sleds are the most current writes for the volume partition. For example, a newly assigned primary head node may present the credentials, e.g. new sequence number, to respective sled controllers to receive respective tokens that supersede tokens previously issued to a previous head node acting as a primary head node for a particular volume or volume partition that had data stored in portions of mass storage devices service by the sled controller. Thus, during a fail over event, a previous primary head node may be fenced off from portions of mass storage devices to prevent corruption of data stored on the mass storage devices during the failover event.

FIG. 1 illustrates a data storage unit comprising head nodes and data storage sleds, according to some embodiments. Data storage unit 100, which may be included in a data storage system, includes network switches 102 and 104, head nodes 106 and data storage sleds 134-144 on shelves 118. Each data storage sled 134-144 includes a sled controller 112 and mass storage devices 110. The head nodes 106, data storage sleds 134-144, and network switches 102 and 104 are mounted in rack 130. In some embodiments, networking devices, such as network switches 102 and 104, may be mounted in a position adjacent to and external from a rack of a data storage unit, such as rack 130 of data storage unit 100. A data storage unit may have redundant network connections to a network external to the data storage unit, such as network 128 that is connected to both network switch 102 and network switch 104. In some embodiments, components of a data storage unit, such as network switches 102 and 104, head nodes 106, and data storage sleds 134-144 may be connected to redundant power sources. For example, power connections 108 indicate power connections for network switches 102 and 104, head nodes 106, and data storage sleds 134-144. Note that power connections 108 are illustrated as a power symbol for simplicity of illustration, but may include various types of power connectors and power distribution systems. For example, power connectors of data storage unit components, such as head nodes and data storage sleds, may couple to dual power distribution systems within a data storage unit that receive power from dual power sources. In some embodiments, a data storage unit may include more than two redundant power distribution systems from more than two redundant power sources.

Each head node of a data storage unit, such as each of head nodes 106, may include a local data storage and multiple network interface cards. For example, a head node may include four network ports, wherein two network ports are used for internal communications with data storage sleds of a data storage unit, such as data storage sleds 134-144, and two of the network ports are used for external communications, for example via network 128. In some embodiments, each head node may be assigned two publicly routable network addresses that are routable from client devices in network 128 and may also be assigned two local network addresses that are local to a data storage unit and are routable for communications between the head node and data storage sleds of the data storage unit. Thus, a data storage unit, such as data storage unit 100, may include multiple redundant networks for communications within the data storage unit. In some embodiments, publicly routable network addresses may be used for internal communications between head nodes and data storage sleds and a head node may be assigned four publicly routable network addresses that are routable from client devices in network 128. The data storage unit may also include redundant power distribution throughout the data storage unit. These redundancies may reduce risks of data loss or downtime due to power or network failures. Because power and network failure risks are reduced via redundant power and network systems, volumes may be placed totally or at least partially within a single data storage unit while still meeting customer requirements for reliability and data durability.

Also, one or more head nodes of a data storage unit, such as one or more of head nodes 106, may function as a head node and additionally implement a local control plane for a data storage unit. In some embodiments, a local control plane may be implemented in a logical container separate from other control and storage elements of a head node. A local control plane of a data storage unit may select amongst any of the head nodes, such as any of head nodes 106, of the data storage unit when selecting a head node to designate as a primary head node for a volume or volume partition and may select amongst any of the remaining head nodes of the data storage unit when selecting two or more head nodes to designate as reserve head nodes for the volume or volume partition. For example a first one of head nodes 106 may be designated as a primary head node for a volume or volume partition and any of the remaining head nodes 106 may be selected as reserve head nodes for the volume or volume partition. In some embodiments, a given one of the head nodes 106 may be designated as a primary head node for a given volume or volume partition and may also be designated as a reserve head node for another volume or volume partition.

Additionally, any head node may be assigned or select columns of space on mass storage devices in any of the data storage sleds of a data storage unit for storing data for a particular volume or volume partition. For example, any of head nodes 106 may reserve columns of space in mass storage devices 110 in any of data storage sleds 134-144. However, any particular column of space of a mass storage device may only be assigned to a single volume or volume partition at a time.

Because multiple head nodes and multiple data storage sleds are available for selection, and because each volume partition may be assigned two or more reserve head nodes, a failure of a particular head node or a failure of a mass storage device in a particular data storage sled may not significantly reduce durability of data stored in the data storage unit. This is because, upon failure of a head node, a local control plane may designate another head node of the data storage unit to function as a replacement reserve head node for a volume or volume partition. Thus, the volume is only without a secondary head node if two or more of the reserve head nodes for the volume fail, and in that rare circumstance, the volume is only without a secondary head node for a short period of time during which a replacement reserve head node is being designated and index data is being replicated from the primary head node to the replacement reserve head node. Furthermore, when a head node of a data storage unit fails, other head nodes of the data storage unit may still be able to access data in all of the storage sleds of the data storage unit. This is because no single data storage sled is exclusively assigned to any particular head node, but instead columns of space on individual mass storage devices of the data storage sleds are assigned to particular head nodes for particular volumes or volume partitions. This arrangement greatly reduces the blast radius of a head node failure or a disk failure as compared to other storage systems in which each server has a dedicated set of storage devices.

As discussed in more detail below, in some embodiments, a head node or local control plane of a data storage unit may be configured to replicate data stored on mass storage devices that are located in a data storage sled to other mass storage devices in other data storage sleds. Thus, for example, when a data storage sled with a failed mass storage device is removed from a data storage unit for replacement or repair, data from one or more non-failed mass storage devices in a data storage sled may still be available because the data has been replicated to other data storage sleds of the data storage unit. For example, if a single mass storage device 110 in data storage sled 134 failed, data stored in the remaining mass storage devices 110 of data storage sled 134 may be replicated to mass storage devices 110 in any of data storage sleds 136-144. Thus while data storage sled 134 is removed from data storage unit 100 for repair or replacement of the failed mass storage device 110, data previously stored on the non-failed mass storage devices 110 of data storage sled 134 may still be available to head nodes 106.

Also, a data storage unit, such as data storage unit 100, may perform read and write operations independent of a zonal control plane. For example, each of head nodes 106 may be assigned one or more network addresses, such as IP addresses, that are advertised outside of data storage unit 100. Read and write requests may be routed to individual head nodes at the assigned network addresses of the individual head nodes via networking devices of the data storage unit, such as network switches 102 and 104, without the read and write requests being routed through a control plane external to the data storage unit, such as a control plane external to data storage unit 100.

In some embodiments, a data storage sled, such as one of data storage sleds 134-144, may include a sled controller, such as one of sled controllers 112. A sled controller may present the mass storage devices of the data storage sled to the head nodes as storage destination targets. For example head nodes and data storage sleds may be connected over an Ethernet network. In some embodiments, head nodes, such as head nodes 106 may communicate with mass storage devices 110 and vice versa via sled controllers 112 using a Non-volatile Memory Express (NVMe) protocol, or other suitable protocols. In some embodiments, each head node may be assigned multiple private network addresses for communication with data storage sleds over redundant internal Ethernet networks internal to a data storage unit. In some embodiments, a head node at an I/O processing software layer may perform a local disk operation to write or read from a mass storage device of a data storage sled and another software layer of the head node may encapsulate or convert the I/O operation into an Ethernet communication that goes through a networking device of the data storage unit to a sled controller in one of the data storage sleds of the data storage unit. A network interface of a head node may be connected to a slot on a motherboard of the head node, such as a PCIe slot, so that the mass storage devices of the data storage sleds appears to the operating system of the head node as a local drive, such as an NVMe drive. In some embodiments, a head node may run a Linux operating system or other type of operating system. The operating system may load standard drivers, such as NVMe drivers, without having to change the drivers to communicate with the mass storage devices mounted in the data storage sleds.

In some embodiments, a local control plane may be configured to designate more than one head node as a reserve/back-up head node for a volume or a volume partition and also adjust a number of mass storage devices that make up a RAID array for longer term storage of data for the data volume or volume partition. Thus if increased durability is desired for a particular volume or volume partition, the volume data may be replicated on “N” head nodes and subsequently stored across “M” mass storage devices in data storage sleds of the data storage unit, wherein the number “N” and the number “M” may be adjusted to achieve a particular level of durability. In some embodiments, such an arrangement may allow high levels of durability to be realized without having to store data for a data volume outside of a single data storage unit. Also, in such an arrangement, input/output operations may be performed more quickly because data for a particular volume is stored within a single data storage unit.

Also, a given head node may be designated as a primary head node or a reserve head node for multiple volumes. Furthermore, a zonal control plane of a data storage system or a local control plane of a data storage unit may balance volume placement across head nodes of a data storage unit. Because volumes are distributed amongst the head nodes, variations in peak IOPS to average IOPS may be reduced because while one volume may experience peak load other volumes serviced by a particular head node may experience less than peak IOPS load. In some embodiments, a zonal or local control plane may adjust head node designations or volume assignments to balance loads if volumes on a particular head node experience significantly more IOPS than volumes serviced by other head nodes.

While, FIG. 1 illustrates mass storage devices 110 as solid state drives, any suitable storage device may be used. For example, in some embodiments, storage devices 110 may include hard disk drives. Also, FIG. 1 illustrates networking devices 102 and 104 to be networking switches. However, in some embodiments, other suitable networking devices may be used such as routers, etc.

In some embodiments, a data storage unit, such as data storage unit 100, may be part of a larger provider network system. Also, in some embodiments more than one data storage unit may be included in a block storage service of a provider network. For example, FIG. 2 illustrates such an example provider network, according to some embodiments.

FIG. 2 is a block diagram illustrating a provider network that includes multiple network-based services such as a block-based storage service that implements dynamic resource creation to connect with client resources, according to some embodiments. Provider network 200 may be set up by an entity such as a company or a public sector organization to provide one or more services (such as various types of cloud-based computing or storage) accessible via the Internet and/or other networks to clients 210. Provider network 200 may include numerous data centers hosting various resource pools, such as collections of physical and/or virtualized computer servers, storage devices, networking equipment and the like (e.g., computing device 2100 described below with regard to FIG. 21), needed to implement and distribute the infrastructure and services offered by the provider network 200. In some embodiments, provider network 200 may provide computing resources, such as virtual compute service 240, storage services, such as block-based storage service 220, and/or any other type of network-based services 260. Clients 210 may access these various services offered by provider network 200 via network 270. Likewise network-based services may themselves communicate and/or make use of one another to provide different services. For example, computing resources offered to clients 210 in units called “instances,” such as virtual or physical compute instances, may make use of particular data volumes 226, providing virtual block-based storage for the compute instances. Also, note that any of the data storage units 224 a, 224 b, 224 n may be data storage units such as data storage unit 100 illustrated in FIG. 1.

As noted above, virtual compute service 240 may offer various compute instances, such as compute instances 254 a and 254 b to clients 210. A virtual compute instance may, for example, comprise one or more servers with a specified computational capacity (which may be specified by indicating the type and number of CPUs, the main memory size, and so on) and a specified software stack (e.g., a particular version of an operating system, which may in turn run on top of a hypervisor). A number of different types of computing devices may be used singly or in combination to implement the compute instances of virtual compute service 240 in different embodiments, including special purpose computer servers, storage devices, network devices and the like. In some embodiments instance clients 210 or any other user may be configured (and/or authorized) to direct network traffic to a compute instance. In various embodiments, compute instances may mount, connect, attach or map to one or more data volumes 226 provided by block-based storage service 220 in order to obtain persistent block-based storage for performing various operations.

Compute instances may operate or implement a variety of different platforms, such as application server instances, Java™ virtual machines (JVMs), special-purpose operating systems, platforms that support various interpreted or compiled programming languages such as Ruby, Perl, Python, C, C++ and the like, or high-performance computing platforms) suitable for performing client applications, without for example requiring the client 210 to access an instance.

Compute instance configurations may also include compute instances with a general or specific purpose, such as computational workloads for compute intensive applications (e.g., high-traffic web applications, ad serving, batch processing, video encoding, distributed analytics, high-energy physics, genome analysis, and computational fluid dynamics), graphics intensive workloads (e.g., game streaming, 3D application streaming, server-side graphics workloads, rendering, financial modeling, and engineering design), memory intensive workloads (e.g., high performance databases, distributed memory caches, in-memory analytics, genome assembly and analysis), and storage optimized workloads (e.g., data warehousing and cluster file systems). Size of compute instances, such as a particular number of virtual CPU cores, memory, cache, storage, as well as any other performance characteristic. Configurations of compute instances may also include their location, in a particular data center, availability zone, geographic, location, etc., and (in the case of reserved compute instances) reservation term length.

As illustrated in FIG. 2, a virtualization host, such as virtualization hosts 242 a and 242 n, may implement and/or manage multiple compute instances 252 a, 252 b, 254 a, and 254 b respectively, in some embodiments, and may be one or more computing devices, such as computing device 2100 described below with regard to FIG. 21. Virtualization hosts 242 may also provide multi-tenant hosting of compute instances. For example, in some embodiments, one virtualization host may host a compute instance for one entity (e.g., a particular client or account of virtual computing service 210), while another compute instance hosted at the same virtualization host may be hosted for another entity (e.g., a different account). A virtualization host may include a virtualization management module, such as virtualization management modules 244 a and 244 b capable of instantiating and managing a number of different client-accessible virtual machines or compute instances. The virtualization management module may include, for example, a hypervisor and an administrative instance of an operating system, which may be termed a “domain-zero” or “dom0” operating system in some implementations. The dom0 operating system may not be accessible by clients on whose behalf the compute instances run, but may instead be responsible for various administrative or control-plane operations of the network provider, including handling the network traffic directed to or from the compute instances.

Virtual computing service 240 may implement control plane 250 to perform various management operations. For instance, control plane 250 may implement resource management to place compute instances, and manage the access to, capacity of, mappings to, and other control or direction of compute instances offered by provider network. Control plane 250 may also offer and/or implement a flexible set of resource reservation, control and access interfaces for clients 210 via an interface (e.g., API). For example, control plane 250 may provide credentials or permissions to clients 210 such that compute instance control operations/interactions between clients and in-use computing resources may be performed.

In various embodiments, control plane 250 may track the consumption of various computing instances consumed for different virtual computer resources, clients, user accounts, and/or specific instances. In at least some embodiments, control plane 250 may implement various administrative actions to stop, heal, manage, or otherwise respond to various different scenarios in the fleet of virtualization hosts 242 and instances 252, 254. Control plane 250 may also provide access to various metric data for client(s) 210 as well as manage client configured alarms.

In various embodiments, provider network 200 may also implement block-based storage service 220 for performing storage operations. Block-based storage service 220 is a storage system, composed of one or more computing devices implementing a zonal control plane 230 and a pool of multiple data storage units 224 a, 224 b through 224 n (e.g., data storage units such as data storage unit 100 illustrated in FIG. 1), which provide block level storage for storing one or more sets of data volume(s) 226 a, 226 b through 226 n. Data volumes 226 may be attached, mounted, mapped, or otherwise connected to particular clients (e.g., a virtual compute instance of virtual compute service 240), providing virtual block-based storage (e.g., hard disk storage or other persistent storage) as a contiguous set of logical blocks. In some embodiments, a data volume 226 may be divided up into multiple data chunks or partitions (including one or more data blocks) for performing other block storage operations, such as snapshot operations or replication operations. A volume snapshot of a data volume 226 may be a fixed point-in-time representation of the state of the data volume 226. In some embodiments, volume snapshots may be stored remotely from a data storage unit 224 maintaining a data volume, such as in another storage service 260. Snapshot operations may be performed to send, copy, and/or otherwise preserve the snapshot of a given data volume in another storage location, such as a remote snapshot data store in other storage service 260. In some embodiments, a block-based storage service, such as block-based storage service 220, may store snapshots of data volumes stored in the block-based storage service.

Block-based storage service 220 may implement zonal control plane 230 to assist in the operation of block-based storage service 220. In various embodiments, zonal control plane 230 assists in creating volumes on data storage units 224 a, 224 b, through 224 n and moving volumes between data storage units 224 a, 224 b, through 224 n. In some embodiments, access to data volumes 226 may be provided over an internal network within provider network 200 or externally via network 270, in response to block data transaction instructions.

Zonal control plane 230 may provide a variety of services related to providing block level storage functionality, including the management of user accounts (e.g., creation, deletion, billing, collection of payment, etc.). Zonal control plane 230 may implement capacity management, which may generate and manage a capacity model for storage service 220, and may direct the creation of new volumes on particular data storage units based on the capacity of storage service 220. Zonal control plane 230 may further provide services related to the creation and deletion of data volumes 226 in response to configuration requests.

Clients 210 may encompass any type of client configured to submit requests to network provider 200. For example, a given client 210 may include a suitable version of a web browser, or may include a plug-in module or other type of code module configured to execute as an extension to or within an execution environment provided by a web browser. Alternatively, a client 210 may encompass an application such as a database application (or user interface thereof), a media application, an office application or any other application that may make use of compute instances, a data volume 226, or other network-based service in provider network 200 to perform various operations. In some embodiments, such an application may include sufficient protocol support (e.g., for a suitable version of Hypertext Transfer Protocol (HTTP)) for generating and processing network-based services requests without necessarily implementing full browser support for all types of network-based data. In some embodiments, clients 210 may be configured to generate network-based services requests according to a Representational State Transfer (REST)-style network-based services architecture, a document- or message-based network-based services architecture, or another suitable network-based services architecture. In some embodiments, a client 210 (e.g., a computational client) may be configured to provide access to a compute instance or data volume 226 in a manner that is transparent to applications implemented on the client 210 utilizing computational resources provided by the compute instance or block storage provided by the data volume 226.

Clients 210 may convey network-based services requests to provider network 200 via external network 270. In various embodiments, external network 270 may encompass any suitable combination of networking hardware and protocols necessary to establish network-based communications between clients 210 and provider network 200. For example, a network 270 may generally encompass the various telecommunications networks and service providers that collectively implement the Internet. A network 270 may also include private networks such as local area networks (LANs) or wide area networks (WANs) as well as public or private wireless networks. For example, both a given client 210 and provider network 200 may be respectively provisioned within enterprises having their own internal networks. In such an embodiment, a network 270 may include the hardware (e.g., modems, routers, switches, load balancers, proxy servers, etc.) and software (e.g., protocol stacks, accounting software, firewall/security software, etc.) necessary to establish a networking link between given client 210 and the Internet as well as between the Internet and provider network 200. It is noted that in some embodiments, clients 210 may communicate with provider network 200 using a private network rather than the public Internet.

Data Replication

FIG. 3A is a block diagram illustrating head nodes and data storage sleds of a data storage unit storing block storage data in response to a write request, according to some embodiments. Head nodes 304, 306, 308, 310, and 312 illustrated in FIGS. 3A-3B may be the same as head nodes 106 illustrated in FIG. 1. Also, data storage sleds 330 may be the same as data storage sleds 134-144 illustrated in FIG. 1.

As discussed above, a data storage system that includes a data storage unit, may store volume data in a data storage of a first head node designated as a primary head node for a volume or volume partition and may also replicate the volume data to additional head nodes designated as reserve head nodes for the volume or volume partition. For example, at time 1, a write request 302 is routed to head node 306 that is designated as a primary head node for a volume or volume partition. At time 2 subsequent to the write request being received at head node 306, data included with the write request is stored in storage 316 of primary head node 306 and primary head node 306 causes the data included with the write request to be replicated to storages 318 and 320 of reserve head nodes 308 and 310, respectively. Replication of the data to reserve head nodes 308 and 310 is performed concurrently or nearly concurrently with storing the data in storage 316 of primary head node 306. Also, as shown in FIG. 3A at time 2, replication of the data to the reserve head nodes may include the reserve head nodes sending an acknowledgment back to the primary head node indicating that the data has been replicated to the reserve head nodes. Subsequently at time 3, which is also nearly concurrent with the data being stored in the storage of the primary head node and the data being replicated to the reserve head nodes, the primary head node, head node 306, may issue an acknowledgement 324 to the client device that requested write 302 has been committed in data storage system 300.

In some embodiments, a write request, such as write request 302, may be concurrently received at a primary head node and a reserve head node. In such embodiments, the primary head node may verify that the reserve head node has committed the write before acknowledging at time 3 that the write has been committed in the data storage system.

At a later point in time 4, e.g. asynchronous to times 1-3, the primary head node, e.g. head node 306, may cause data stored in storage 316, that includes the data included with the write request and that may include additional data stored before or after the write request, to be flushed to mass storage devices 326 of the data storage sleds 330 of the data storage unit. For example, at time 4 data is flushed to mass storage devices 326 of data storage sleds 330. In some embodiments, data is divided into portions and stored across multiple mass storage devices, each in a different sled and/or on a different shelf of a data storage unit. In some embodiments, data is also erasure encoded when stored in mass storage devices of data storage sleds. For example, data flushed from storage 316 of head node 306 may be divided into six portions where each portion is stored in a different mass storage device of a different data storage sled on a different shelf of a data storage unit 350 of data storage system 300 and is also erasure encoded across the different mass storage devices. For example data portions are stored in sled A of shelf 1, sled B of shelf 2, sled A of shelf 3, sled C of shelf 4, sled B of shelf 5, and sled C of shelf 6.

Also, as can be seen in FIG. 3A, a data storage unit, such as data storage unit 350, may include “M” number of shelves and “N” number of head nodes. The portions of data may be stored on portions of mass storage devices 326 in the respective data storage sleds 330. In order to distinguish between a portion of data and a portion of space on a mass storage device, a portion of space on a mass storage device may be referred to herein as a “column” of a mass storage device. Furthermore, a set of columns of mass storage devices that store different portions of data of a volume such as the columns shown in sled A of shelf 1, sled B of shelf 2, sled A of shelf 3, sled C of shelf 4, sled B of shelf 5, and sled C of shelf 6 may collectively make up what is referred to herein as an “extent.” For example, in an erasure encoded RAID six array, an extent may include six columns that collectively make up the RAID array. Four of the columns may store striped data and two of the columns may store parity data. In some embodiments, other replication algorithms other than erasure encoding may be used such as quorum algorithms, etc.

In some embodiments, each column of an extent may be in a different fault domain of a data storage unit. For example, for the extent being stored in FIG. 3A each column is located in a different data storage sled that is mounted on a different shelf of the data storage unit 350. Thus a failure of a sled controller, such as one of sled controllers 328, may only affect a single column. Also if a power supply of a data storage sled fails it may only affect a single data storage sled or if a part of a power distribution system fails it may affect a single shelf. However, because each column of an extent may be located in a different shelf, a shelf level power event may only affect a single column of the extent.

In some embodiments, a head node of a data storage unit, such as one of head nodes 304, 306, 308, 310, or 312, may implement a local control plane. The local control plane may further implement an extent allocation service that allocates extents to head nodes designated as a primary head node for a volume or volume partition. In some embodiments, an extent allocation service may allocate a set of extents to a particular volume referred to herein as a “sandbox.” The primary head node for the particular volume may then select extents to store data on during a data flush from the primary head node to data storage sleds of the data storage unit by selecting an extent from the sandbox allocated for the particular volume.

In some embodiments, if insufficient space is available in the particular volume's sandbox or if a particular placement would cause a data durability of data to be saved to fall below a minimum required durability for the particular volume, a primary head node for the particular volume may select columns outside of the particular volume's sandbox to write data for the particular volume. For example, a sandbox may include multiple columns that make up multiple extents in different ones of the data storage sleds 330 on different ones of the shelves of a data storage unit 350. A primary head node may be able to flush data to columns within a particular volume's sandbox without having to request extent allocation from a local control plane that implements an extent allocation service. This may further add durability and reliability to a data storage unit because a primary head node for the particular volume may continue to flush data even if communication is lost with a local control plane within the data storage unit. However, if space is not available or a placement would cause durability for a particular volume or volume partition to fall below a minimum threshold, a primary head node may flush data to columns outside of the particular volume's sandbox. In some embodiments, a primary head for a particular volume may flush data to columns outside the primary head node's sandbox without requesting an allocation from a local control plane that implements an extent allocation service. For example, a primary head node may store addresses for each sled controller in a data storage unit and may flush data to any sled controller in the data storage unit that is associated with mass storage devices with available columns.

As will be discussed in more detail in regard to FIG. 19, a sled controller of a data storage sled, such as sled controller 328, may implement a fencing protocol that prevents a primary head node from writing to columns for which another primary head node has assumed control after the primary head node has been superseded by another head node assuming the role of primary head node for a particular volume or volume partition. It should be pointed out that a reserve head node or other back-up head nodes may not flush data to data storage sleds and flushing may be limited to only being performed by a primary head node.

Because for a particular volume, the volume's data may be stored in a storage of a primary head node and replicated to a reserve head nodes and may later be moved to being stored across an extent of mass storage devices in different data storage sleds of a data storage unit, metadata comprising an index with pointers to where the data is stored may be used for subsequent read requests and write requests to locate the data. Also in some embodiments, storages of a head node may be log-structured such that incoming write request are written to the head of the log of the head node's log-structured storage. An index entry may be added indicating where the written data is stored in the head node's log and subsequently the index may be updated when the written data is flushed from the log of the primary head node to an extent comprising columns of mass storage devices of the data storage system.

In some embodiments, replication to the reserve head nodes may be performed synchronously with a write, whereas flushing of stored data, such as write data, from a primary head node to an extent implemented on a set of mass storage devices of the data storage sleds may be performed asynchronously with a write or a set of writes. For example, replicated writes to head nodes 308 and 310 from primary head node 306 may be performed synchronously with servicing write request 302 and prior to sending acknowledgment 324. Also, for example, flushing of data to data storage sleds 330 (performed at time 4) may be performed asynchronously with servicing write request 302 and after sending acknowledgment 324.

In some embodiments, a replicated write, replicated from a primary head node to a reserve head node, may include a current sequence number for the head nodes of a group of head nodes designated as primary or reserve head nodes for a particular volume partition to which the write is directed. In some embodiments, a reserve head node may store a greatest sequence number yet seen for the particular volume partition and may decline to perform a replicated write if a sequence number appended to a replicated write is inferior to a sequence number stored by the reserve head node for the particular volume partition.

In some embodiments, a primary head node, such as primary head node 306, may wait to receive a commitment acknowledgment from two or more reserve head nodes, such as reserve head nodes 308 and 310, before providing a commitment acknowledgement back to a client, such as acknowledgement 324. For example, primary head node 306 may refrain from sending acknowledgment 324 until head node 308 and 310 have indicated that the volume data being replicated to head nodes 308 and 310 at time 2 has been written to storages 318 and 320 of the respective head nodes 308 and 310.

As further discussed below, in some embodiments, in response to detecting a lagging or slow reserve head node of a set of head nodes designated to store replicas for a particular volume partition, the set of head nodes for the particular volume partition may enter an asynchronous state. In an asynchronous state, one of the two or more reserve head nodes for the particular volume partition may be dropped from the requirement to acknowledge a replicated write before the write can be acknowledged as committed in the data storage system to a client of the data storage system. For example, a new sequence number may be issued to a set of head nodes that does not include the slow or lagging reserve head node. Also, the slow or lagging reserve head node may be removed from a membership group for the set of head nodes for the particular volume partition. However, the slow or lagging reserve head node may continue to receive replicated writes and may attempt to catch-up state with one or more remaining non-slow reserve head nodes included in the membership group for the particular volume partition. If the slow reserve head node successfully catches up to the remaining reserve head node(s) of the membership group, a new sequence number may be issued to the group and the group membership may be changed to include the previously slow or lagging reserve head node as one of the two or more reserve head nodes for the particular volume partition. Furthermore, the primary head node may revert to waiting for an acknowledgment from the previously slow or lagging reserve head node prior to acknowledging a write has been committed in the data storage system to a client.

In some embodiments, if a slow or lagging reserve head node fails to catch-up to a remaining reserve head node(s) for a membership group within a threshold amount of time, or within another threshold, such as a number of operations, an amount of data lagging, etc., the slow or lagging reserve head node may be replaced with another reserve head node designated to host a replica for the particular volume partition. For example, the data storage system may initiate a fast-failover for a reserve replica of the particular volume partition to a new replacement reserve head node. In some embodiments, this may be done preemptively prior to a full failure of the slow or lagging reserve head node. In some embodiments, the membership group for the particular volume partition may be updated to include the replacement reserve head node and a new sequence number may be issued to the members of the updated membership group for the particular volume partition. Also, in some embodiments, if a slow or lagging reserve head node has fallen out of a membership group for a particular volume partition and returned to a membership group for the particular volume partition more than a threshold number of times in a given time unit, the data storage system may initiate a fast fail-over for a reserve replica hosted by the slow or lagging reserve head node. In some embodiments, a data storage system may initiate a fast fail-over for a slow or lagging reserve head node based on a number of volume partitions for which the head node is determined to be slow or lagging.

In some embodiments, during initialization, a control plane of a data storage unit or data storage system may first designate a primary head node for a particular volume partition being initialized and may issue a sequence number to the primary head node, wherein the membership group for the particular volume partition being initialized comprises the primary head node. The control plane may then designate a first reserve head node for the particular volume partition being initialized and may issue a new sequence number to both the primary head node and the first reserve head node, wherein the membership group associated with the new sequence number includes the primary head node and the first reserve head node. The control plane may then designate a second reserve head node for the particular volume partition being initialized and may issue another new sequence number to the primary head node, the first reserve head node, and the second reserve head node. At this stage, the membership group associated with the other new sequence number may include the primary head node, the first reserve head node, and the second reserve head node. In some embodiments, upon a change in membership of a membership group for a particular volume partition, the control plane may issue a new sequence number to head nodes that are included in the changed membership group.

In some embodiments, a data storage unit, such as data storage unit 350, may store more “full” copies of volume data for a volume partition in the head nodes than is stored once the volume data has been flushed to the data storage sleds. For example, in some embodiments three or more “full” copies of volume data may be stored in the head nodes with a first copy stored on a primary head node and two or more additional copies stored on two or more reserve head nodes. In some embodiments, volume data stored to the data storage sleds may be erasure encoded, such that, as an example, the flushed data comprises 1.5 “full” copies of the volume data. For example, the storage of four striped columns and two parity columns (as discussed in more detail in FIGS. 6A-6B) may result in 1.5 “full” copies of the volume data being stored in the data storage sleds. However, as shown in FIG. 3A, the flushed data may be stored across more separate storage devices in the data storage sleds than the data was stored across in the head nodes. For example, the flushed volume data may be stored on six different mass storage devices in six different data storage sleds, whereas the volume data, prior to being flushed, may have been stored on three head nodes (a primary head node and two reserve head nodes). In some embodiments, volume data may be replicated to more or fewer head nodes. Also, in some embodiments other erasure encoding schemes may be used to store more or fewer copies of volume data in the data storage sleds on more or fewer separate mass storage devices in separate data storage sleds.

FIG. 3B is a block diagram illustrating head nodes of a data storage unit re-mirroring data to a replacement head node for a volume partition, according to some embodiments.

As discussed above, in response to a failure of a reserve head node, such as reserve head node 310, a control plane of a data storage system or a data storage unit, such as a control plane of data storage system 300 or a local control plane of data storage unit 350, may designate another head node of the data storage unit as a reserve head node for a particular volume partition, wherein the reserve head node hosts a reserve replica of the particular volume partition. For example, a control plane may designate head node 312 as a replacement reserve replica. Additionally, a new sequence number may be issued for the head nodes hosting replicas for the particular volume partition. For example, a new sequence number may be issued to primary head node 306, reserve head node 308, and replacement reserve head node 312.

In some embodiments, a primary head node, such as primary head node 306, may re-mirror volume partition data to the replacement reserve head node. For example, head node 306 performs re-mirroring 322 to replicate volume data and volume metadata (such as log index data) to the replacement reserve head node 312. The primary head node may include a newly issued sequence number with the data being re-mirrored to the replacement reserve head node. Also, the replacement reserve head node may not accept writes for the particular volume that include a sequence number inferior to the greatest sequence number for the volume partition seen by the replacement reserve head node. This may prevent a partially failed primary or reserve head node that has been removed from a membership group for a particular volume partition from overwriting volume data for the volume partition. For example, a failed or partially failed head node presenting a sequence number for a previous membership group for a particular volume partition would be prevented from causing data to be written for the particular volume partition on a head node included in a current membership group for the particular volume partition. This is because the former primary head node would have an inferior (e.g. smaller) sequence number than the current sequence number for the current membership group for the particular volume partition.

In some embodiments, a primary head node, such as head node 306, may delegate one or more re-mirroring tasks to a reserve head node. For example, primary head node 306 may delegate a re-mirroring task to reserve head node 308, such as to replicate volume data to replacement reserve head node 312. In some embodiments, this may free up IO capacity on a primary head node to service client read requests while volume data is being read from a surviving reserve head node and replicated to a replacement reserve head node.

FIGS. 4A-4B are block diagrams illustrating a log-structured storage and an index of a head node storage, according to some embodiments. Head node 402 includes storage 404 that includes log 408 and index 406. Volume data may be stored in log 408 prior to being flushed to mass storage devices of a data storage unit. Index information 410 may include an entry for the volume data and a corresponding pointer to where the volume data is stored. For example, index information 410 indicates that data for volume 1, offset A, length B is stored in log storage 408 at log segment C and offset D. In some embodiments, a log of a head node such as log 408 of storage 404 of head node 402 may store data for more than one volume. For example, index information 410 also includes an entry for volume 2 offset E, length F and a corresponding pointer indicating the data for this volume entry is stored in log 408 at log segment G, offset H.

While FIGS. 4A-B illustrate log storage 408 and index 406 as separate from each other, in some embodiments, an index, such as index 406, may lay on top of a log or side-by-side with a log, such as log storage 408.

When data for a volume is moved from a storage of a head node to being stored in an extent across multiple mass storage devices of a data storage unit, the data for the volume may be removed from a log of a head node storage and an index of the head node storage may be updated to indicate the new location at which the data for the volume is stored. For example, in FIG. 4B, index information 412 indicates that data for volume 1, offset A, length B is now stored at extent A, offset X and data for volume 2, offset E, length F is now stored at extent B, offset Y. Note that the labels “extent A” and “extent B” are used for ease of illustration. In some embodiments, an index may include addresses of data storage sleds where the data for the volume is located, such as local IP addresses of the data storage sleds, and addresses of the columns of the mass storage devices within the data storage sleds. In some embodiments, an index may include another label such as “extent A” where each head node stores information for locating “extent A” or may consult an extent allocation service for locating “extent A.” In some embodiments, an index may include addresses of data storage sleds where the data for the volume is located and sled controllers of the data storage sleds may be able to determine the appropriate columns based on volume IDs stored in respective columns allocated to the volume.

When a read request is received by a head node designated as a primary head node for a volume, the head node may consult an index of a storage of the head node, such as index 406 of storage 404, to determine what is the latest version of the volume's data and where the latest version of the volume's data is stored. For example a primary head node, such as head node 402, may consult the primary head node's index, such as index 406, to determine if the latest version of the volume's data is stored in the head node's log, such as log 408, or is stored in an extent comprising mass storage devices of the data storage unit.

FIG. 5 illustrates a partial view of a data storage unit that stores portions of a volume partition in multiple mass storage devices in multiple data storage sleds on multiple shelves of the data storage unit, according to some embodiments. FIG. 5 illustrates an example storage pattern for extent A from index 406 in FIG. 4B. Extent A from index 406 illustrated in FIG. 4B is shown as extent A 502 in FIG. 5 Also, an example storage pattern for extent B from index 406 illustrated in FIG. 4B is shown in FIG. 5 as extent B 504. Note that a data storage sled may include multiple columns of multiple extents. Also, in some embodiments a single mass storage device may include multiple columns of multiple extents.

FIGS. 6A-B illustrate columns of mass storage devices storing different portions of a volume partition, according to some embodiments. FIG. 6A illustrates an embodiment in which data flushed to extent A, which may be the same extent A as described in FIGS. 4 and 5, is erasure encoded across 4+2 columns. The striped data 602 may include the original data flushed from log 408 divided into multiple portions and the parity data 604 may include encoded data that allows the flushed data to be recreated in case of failure of one or more of the mass storage devices or sleds that include one of the columns. FIG. 6B illustrates a similar embodiment where extent B is erasure encoded across four striped data columns 606 and two parity columns 608. Note that in FIG. 6B the data is stored in a different location in the column than is shown in FIG. 6A. This is intended to illustrate that the columns shown in FIG. 6B may already store data previously written to the columns of extent B, whereas the data being written to extent A may be the first set of data written to extent A. Also, it is worth noting that for a particular volume, multiple extents may be assigned to store data of the volume. In some embodiments, an extent may represent a fixed amount of storage space across a set number of columns of mass storage devices. When an extent is filled for a particular volume, another extent may be allocated to the volume by a head node or an extent allocation service. FIGS. 6A and 6B illustrate an example RAID level and erasure encoding technique. However, in some embodiments various other RAID levels may be used and various data coding techniques may be used to increase durability of stored data. It also worth noting that erasure encoding data may reduce a number of columns needed to achieve a particular level of durability. For example, data stored that is not erasure encoded may require the data to be stored redundantly across 8 columns to achieve a given level of durability, whereas a similar level of durability may be achieved by erasure encoding the data across fewer columns. Thus erasure encoding data may significantly reduce an amount of storage resources that are needed to store data to a particular level of durability. For example, data erasure encoded according to a 4+2 erasure coding scheme may be recreated from any four of the six columns, wherein the six columns include four columns of striped data segments and two columns of parity data segments.

In some embodiments, a data storage system may implement one or more communication protocols between head nodes and data storage sleds of the data storage system that allow for rapid communications between the head nodes and the data storage sleds. Thus, high levels of performance may be provided to clients of a data storage system despite volume data being erasure encoded across multiple columns of mass storage devices in different data storage sleds. For example, a data storage system may implement a protocol for reliable out-of-order transmission of packets as described in U.S. patent application Ser. No. 14/983,436 filed on Dec. 29, 2015, which is herein incorporated by reference. Also, for example, a data storage system may implement a protocol for establishing communication between a user application and a target application wherein the network does not require an explicit connection between the user application and the target application as described in U.S. patent application Ser. No. 14/983,431 filed on Dec. 29, 2015, which is herein incorporated by reference. In some embodiments, implementation of such protocols may permit data erasure encoded across multiple mass storage devices in multiple different data storage sleds to be read by a head node in a timely manner such that, from a perspective of a client device of the data storage system, performance is comparable to a system that does not erasure encode volume data across multiple mass storage devices or such that performance exceeds a performance of a system that does not erasure encode volume data across multiple mass storage devices.

FIG. 7 is a high-level flowchart illustrating operations performed by a head node in response to a request to store data in a data storage unit, according to some embodiments.

At 702, a data storage unit receives a write request from a client device directed to a volume partition hosted by the data storage unit and directs the write request to a head node of the data storage unit that is functioning as a primary head node for the volume partition.

At 704, upon receiving the write request from the client device, the head node writes data included with the write request to the log of the head node and updates the index of the head node to include an entry for the volume data and a pointer indicating where the volume data is stored.

At 706, the primary head node causes the data included with the write request to be replicated to two or more reserve head nodes. The reserve head nodes then store the data in respective logs of the reserve head nodes and update respective indexes of the respective storages of the reserve head nodes. For example, each of the reserve head nodes may update an index of the storage of the reserve head node to include an entry for the replicated volume data and a pointer indicating where the replicated volume data is stored. The reserve head nodes may then send respective acknowledgements to the primary head node indicating that the volume data has been replicated in the storages of the reserve head nodes. In some embodiments, the primary head node then issues an acknowledgement to the client device indicating that the requested write has been persisted in the data storage system. In some embodiments, replication between head nodes could be primary and reserve e.g. master/slave replication. In some embodiments, other replication techniques such as a Paxos protocol, other consensus protocol, etc. may be used to replicate data between head nodes.

At 708, the primary head node determines if the log data of the primary head node exceeds a threshold that would trigger the log data or a segment of the primary head node's log data to be flushed to extents that include columns of mass storage devices of data storage sleds of a data storage unit that includes the head node. In some embodiments, a threshold to trigger data to be flushed may include: an amount of data stored in the log or in a segment of the log, an amount of time that has elapsed since the data was last accessed or altered, a frequency at which the data is accessed or altered, or other suitable thresholds. In some embodiments, data flushed from a log of a head node may only include a portion of the data written to the log of the head node or a segment of the log of the head node. For example, older data stored in a log of a head node may be flushed while more recently written data may remain in the log of the head node. In some embodiments, a frequency of flush operations from a log of a head node may be throttled based on a variety of factors, such as a fill rate of the log of the head node or based on an amount of write requests being received by the head node or being received for a particular volume serviced by the head node.

In response to determining the threshold has not been met, the primary head node continues to write data to the log and reverts to 702.

At 710, in response to determining that the threshold has been met or exceeded, the primary head node causes data stored in the log of the primary head node or a segment of the log of the primary head node to be flushed to columns of mass storage devices in different ones of a plurality of data storage sleds of the data storage unit.

At 712, the primary head node updates the log of the primary head node to include a pointer for the volume data indicating that the flushed volume data is now stored in particular columns of mass storage devices or an extent that includes multiple columns of mass storage devices.

At 714, the primary head node causes the reserve head nodes to update respective indexes of the reserve head nodes to indicate the new location of the volume data. The reserve head nodes also release the log space in the reserve head nodes that previously stored the replicated volume data.

At 716, the head node acting as primary head node also releases space in the primary head node's log. In some embodiments, a garbage collection mechanism may cause log space to be released based on inspecting an index of a storage of a head node. In some embodiments, releasing log storage space may be performed concurrently with flushing log data or may be performed at some time subsequent to flushing log data.

FIG. 8A is a high-level flowchart illustrating a replacement head node being designated for a volume partition to replace a failed head node such that two or more reserve head nodes for the volume partition are maintained, according to some embodiments.

At 802, a control plane of a data storage unit determines that a primary head node or a reserve head node for a volume partition has failed or fails to meet one or more performance criteria. For example, a head node failure detection agent, as described in FIG. 10, may fail to receive a response to a ping directed to the head nodes from a failed head node and may alert the control plane or other surviving head nodes of the data storage unit of the failed head node. In some embodiments, the surviving head nodes of the data storage unit may identify volume partitions for which replicas were stored on the failed head node and may request the control plane initiate re-mirroring of replicas for the identified volume partitions that were previously stored on the failed head node. Additionally, as discussed in FIG. 9, a head node may be deemed “failed” as part of a fast-fail over process before the head node is fully failed.

At 804, the control plane designates another head node of the data storage unit as a replacement reserve head node to host a reserve replica for a volume partition for which a replica was previously stored on the failed head node.

At 806, the control plane issues a new sequence number to the replacement reserve head node and the surviving head nodes that are members of an updated membership group for the volume partition for which a replica was previously stored on the failed head node.

FIG. 8B is a high-level flowchart illustrating a replacement head node re-mirroring log data and volume index data from a surviving primary head node or surviving reserve head node, according to some embodiments.

At 852, a replacement reserve head node receives an indication that the head node has been designated as a replacement reserve head node for a volume partition. For example, the indication may include a new sequence number for a membership group for the volume partition that includes the head node as one of two or more reserve head nodes for the volume partition.

At 854, the replacement reserve head node may determine if a sequence number included with volume data or volume metadata being re-mirrored to the replacement reserve head node is equal to or greater than a greatest sequence number previously seen by the replacement reserve head node for the volume partition. For, example the replacement reserve head node may determine if the sequence number matches a sequence number included with the designation of the replacement reserve head node as a reserve head node for the volume partition. If the sequence number matches or exceeds the greatest sequence number previously seen by the replacement reserve head node for the volume partition, the replacement reserve head node may proceed to 856 and re-mirror yet-to-be flushed log data (e.g. volume data) and volume index data (e.g. volume metadata) from one or more surviving head nodes for the volume partition, such as a surviving primary head node or a reserve head node that has been designated by the primary head node to replicate volume data to the replacement reserve head node.

FIG. 8C is a high-level flowchart illustrating a reserve head node enforcing an authorization for a replica for a volume partition, according to some embodiments.

At 872, a reserve head node receives a sequence number with data being replicated to the reserve head node from another head node of the data storage system.

At 874, the reserve head node determines whether the sequence number included with the data to be replicated is greater than or equal to a greatest sequence number previously seen by the particular reserve head node.

At 876, if the sequence number is greater than or equal to the greatest sequence number previously seen by the particular reserve head node, the reserve head node writes the data to be replicated to a storage of the particular reserve head node.

At 878, if the sequence number is not greater than or equal to the greatest sequence number previously seen by the particular reserve head node (e.g. the sequence number is inferior to a previously seen sequence number), the reserve head declines to write the data to be replicated to a storage of the particular reserve head node.

FIG. 9 is a high-level flowchart illustrating a fast failover of a head node with low performance, according to some embodiments.

At 902, a control plane or a primary head node measures write latencies of reserve head nodes for a volume partition. For example, a primary head node may measure an amount of time that elapses between sending a replicated write to a reserve head node and receiving an acknowledgement back from the reserve head node that the replicated write has been written to a storage of the reserve head node.

At 904, the primary head node or a control plane in communication with the primary head node determines if a write latency measured for one or more of the reserve head nodes exceeds a write latency threshold. In some embodiments, the write latency threshold may be selected such that a service level agreement (SLA) or other client guarantee regarding write latency is met.

At 906, a control plane may drop a slow or lagging reserve head node from a membership group for the volume partition. For example, the membership group may be reduced from three head nodes (a primary head node and two reserve head nodes) to two head nodes (a remaining reserve head node and the primary head node). In some embodiments, the control plane may issue a new sequence number to the remaining head nodes in the membership group for the volume partition (e.g. the remaining reserve head node and the primary head node). Upon a failure, the new sequence number may be used to prevent the slow or lagging reserve head node from assuming the role of primary head node and may cause the other remaining reserve head node to be promoted to primary head node upon a failure of the primary head node.

At 908, the primary head node may continue to send replicated writes to the two reserve head nodes (e.g. the remaining reserve head node and the slow or lagging reserve head node). However, the primary head node may only wait on the remaining reserve head node to acknowledge a replicated write before sending an acknowledgement to the client. The primary head node may not wait for the slow or lagging reserve head node to send an acknowledgement to the client before sending an acknowledgment, and may send an acknowledgement to the client prior to the slow or lagging reserve head node acknowledging a replicated write.

At 910, the control plane or the primary head node determines if a write latency for the slow or lagging reserve head node that has been dropped from the membership group for the volume partition has improved to be less than a second write latency threshold. If so, at 914, the dropped reserve head node is added back to the membership group for the volume partition. This may include the control plane issuing a new sequence number to the remaining reserve head node, the previously dropped reserve head node, and the primary head node, wherein the new sequence number reflects the membership change in the membership group. The process may then return to 902.

If at 910, it is determined that the dropped reserve head node has not improved to be less than the second write latency threshold, or another indicator of poor performance has been met, such as an amount of time elapsed in a dropped state, the control plant may initiate a fast-fail over of the dropped reserve head node for the particular volume partition and may also initiate the re-mirroring of volume data and volume metadata for the particular volume partition from the primary head node to a replacement reserve head node.

FIG. 10 is a block diagram illustrating a head node failure detection agent identifying a failed head node, according to some embodiments.

Data storage system 1002, may be a similar data storage system as data storage system 100 illustrated in FIG. 1 and may include one or more data storage units, such as data storage units 224 illustrated in FIG. 2. Additionally, any of the other data storage systems or data storage units as described herein may include a head node failure detection agent as shown in FIG. 10.

In some embodiments, a local control plane of a data storage unit or data storage system may implement a head node failure detection, such as head node failure detection agent 1054. In some embodiments, the local control plane and the head node failure detection agent may be implemented as software modules executing on one or more head nodes of a data storage unit. Also, in some embodiments a separate computer may implement a head node failure detection agent, such as head node failure detection agent 1054.

In some embodiments, a head node failure detection agent, such as head node failure detection agent 1054, may regularly or periodically issue pings, such as pings 1056, to head nodes of a data storage unit, such as head nodes 1004, 1006, 1008, 1010, 1012, 1014, 1016, 10110, 1020, 1022, 1024, and 1026. Each of the head nodes may include a respective log-structured storage such as storages 1030, 1032, 1034, 1036, 1038, 1040, 1042, 1044, 1046, 1048, 1050, and 1052. In some embodiments, a given storage of a given head node may store respective primary replicas for multiple volume partitions stored in data storage system 1002 and multiple reserve replicas for volume partitions stored in data storage system 1002. In some embodiments, placement of primary replicas and reserve replicas may be restricted such that for each volume partition, the volume partition's primary replica and reserve replicas are stored in storages of different head nodes.

In some embodiments, a head node failure detection agent, such as head node failure detection agent 1054, may ping the head nodes using a shallow ping, an intermediate ping, or a deep ping. For example, a “shallow” ping may verify that there is an active network connection to a head node being pinged. In some embodiments, an intermediate ping may query an operating system of a head node being pinged and/or query a log drive, without querying each individual replica stored in the log drive. Also, in some embodiments a “deep” ping may be used wherein the “deep” ping is directed to individual replicas for volume partitions stored on a head node being pinged. In some embodiments, a “shallow” ping may not interact with each replica stored on a head node being pinged and may thus utilize less head node overhead capacity and network capacity than a “deep” ping. For example, a “shallow” ping may not appreciably interfere with a capacity of a head node to service read and write requests, perform replications, or store metadata.

In some embodiments, in response to receiving a ping 1056, each of the head nodes that is not failed may issue a ping response 1058. Thus, a head node failure detection agent, such as head node failure detection agent 1054, may quickly identify a failed head node, such as failed head node 1016, due to the lack of a ping response from the failed head node. In some embodiments, a ping and ping response may be functionally achieved using other messages that are sent between a local control plane and each head node. For example, FIG. 18 discusses a local control plane collecting performance information from head nodes of a data storage unit. In some embodiments, a request for performance information as discussed in FIG. 18 may function as a ping, and a head node reporting performance information may function as a ping response.

In some embodiments, upon identifying a failed head node, a head node failure detection agent, such as head node failure detection agent 1054, may send a failed head node notification 1060 to the surviving head nodes (e.g. the head nodes that have not failed), such as head nodes 1004, 1006, 1008, 1010, 1012, 1014, 1018, 1020, 1022, 1024, and 1026. Additionally, each of the head nodes may identify volume partitions stored by the head node that have primary or reserve replicas stored on the failed head node. For such volume partitions, the surviving head nodes in coordination with a local control plane may initiate re-mirroring to replacement head nodes for the replicas that were stored on the failed head node

FIG. 11A is an example user interface to a block storage service, wherein a client can specify a durability for one or more of the client's volumes, according to some embodiments.

In some embodiments, an interface to a block data storage service, such as interface 1100 may allow a client to specify a durability requirement for a volume to be allocated for the client in the block data storage service. While FIG. 11 illustrates a graphical user interface, in some embodiments, a block data storage service may include other types of interface for receiving a client durability requirement for a volume, such as an application programmatic interface (API), command line interface, etc.

In some embodiments, an interface, such as interface 1100, may include multiple volume request spaces, such as volume request spaces 1102, 1106, and 1110 for volumes that the client requests to be implemented for the client. Additionally, in some embodiments, a user interface, such as interface 1100, may include durability selection areas, such as durability selection areas 1104, 1108, and 1112, in the respective volume request spaces 1102, 1106, and 1110. In some embodiments, a client may select from a pre-defined set of durability requirements, such as standard durability, enhanced durability, superior durability, minimal durability, etc. In some embodiments, a client may specify a durability requirement such as “5-9s” durability or a guarantee that 99.99999% of the client's data will not be lost. Also, in some embodiments an interface, such as interface 1100, may include a submit button 1114 to cause the requested volumes to be implemented with the specified durability characteristics.

While not shown in FIG. 11A, in some embodiments, a client may be able to modify a durability requirement for an already implemented volume.

FIG. 11B is a high-level flowchart illustrating head node replication adjustments or erasure encoding adjustments being made to meet a client's durability requirement for a volume of the client, according to some embodiments.

At 1152, a data storage system receives an indication from a client of a data storage service regarding one or more durability requirements for volume stored in, or to be stored in, the data storage service. For example, the indication may be received via a user interface as described in FIG. 11A.

At 1154, a control plane of the data storage system or a data storage unit in the data storage system, determines if the near term durability requirements in relation to the client specified durability requirement vary from default near term durability guarantees of the data storage system or data storage unit. If so, at 1156, the control plane adjusts a number of reserve replicas that are maintained in the head nodes for the volume. For example in some embodiments, a single primary replica may be maintained for a minimal durability volume, two replicas, a primary replica and a secondary replica may be maintained for a standard durability volume. In some embodiments, a primary replica and two reserve replicas may be maintained for an enhanced durability volume, and a primary and more than two reserve replicas may be maintained for a superior durability volume.

At 1158, the control of the data storage system or a data storage unit in the data storage system, determines if the long term durability requirements in relation to the client specified durability requirement vary from default long term durability guarantees of the data storage system or data storage unit. If so, at 1160, the control plane adjusts an erasure encoding algorithm used to erasure encode volume data flushed to the data storage sleds, such that the flushed volume data includes more or fewer striped columns and more or fewer parity columns stored on mass storage devices of different ones of the data storage sleds.

If not, the data storage system or data storage unit uses the default erasure encoding algorithm and/or the default head node replication scheme to store volume data for the volume.

FIG. 12A is a high-level flowchart illustrating operations performed by a head node in response to a failed mass storage device in a data storage sled of a data storage unit, according to some embodiments.

At 1202, a head node or a sled controller detects a failed mass storage device in a particular data storage sled. For example, a data storage sled may include multiple mass storage devices, such as solid state storage drives, and one of the mass storage devices may fail. In some embodiments, a data storage sled may include disk drives and one of the disk drives may fail. In some embodiments, a data storage sled may include other types of mass storage devices.

At 1204, a head node acting as a primary head node for a volume with extents that include one or more columns on the failed mass storage device or a local control plane for the data storage unit causes the extents that include columns on the failed mass storage device to be replicated to other extents that include columns on other mass storage devices in other sleds of the data storage unit. For example, in a 4+2 erasure coding scheme data from any one lost mass storage drive can be recreated based on data stored on the other mass storage devices that make up an extent. Thus, data previously stored on the failed mass storage device can be recreated and replicated to data storage sleds that do not include a failed mass storage device.

At 1206, indexes of a primary head node and a reserve head node that are designated for each volume that included an extent in the failed mass storage device are updated to indicate the new locations of the data for the volumes.

In some embodiments, a data storage system may continue to operate a data storage sled that includes a failed mass storage device, such as the failed mass storage device at 1208. In some embodiments, step 1206 may be omitted and all extents stored on mass storage devices in the data storage sled that includes the failed mass storage device may be replicated to other data storage sleds. Because the extents that include columns on the failed mass storage device have been replicated to data storage sleds that do not include failed mass storage devices, the durability of the data previously stored on the failed mass storage device has been recovered to the original level of durability. For example in a RAID configuration of six segments, the number of segments is returned to six by replicating the data from the failed mass storage device to other mass storage devices in the data storage unit.

FIG. 12B is a high-level flowchart illustrating operations performed by a head node in response to a failed mass storage device in a data storage sled of a data storage unit, according to some embodiments.

In some embodiments, a data storage system may tolerate one or more failed mass storage devices in a particular sled before the mass storage devices are replaced. For example, at 1252 one or more additional failed mass storage devices are detected in a data storage sled. In some embodiments the additional failed mass storage devices may be in the same data storage sled as the failed mass storage device described in FIG. 12A or may be in a different data storage sled of the data storage unit.

At 1254, data from other non-failed mass storage devices each in a data storage sled that includes a failed mass storage device is copied to other mass storage devices in other data storage sleds of the data storage unit. In some embodiments, only data from non-failed mass storage devices that are included in a data storage sled that is to be repaired may be copied. In some embodiments, copying the data from the non-failed mass storage devices may include recreating the data from a set of columns stored on remaining non-failed mass storage devices and then erasure encoding the data across another set of columns of mass storage devices of a replacement extent. For example, in a 4+2 erasure encoding scheme, data of an extent may be recreated from any four of the six columns of the extent. After being recreated, the data may be erasure encoded across another set of 4+2 columns of a replacement extent.

At 1256, indexes of a primary head node and a reserve head node that are designated for each volume that included an extent in the affected mass storage devices are updated to indicate the new locations of the data for the volumes that has been copied to other mass storage devices in the data storage unit.

At 1258, the data storage sled(s) that includes the failed mass storage device is at least partially removed from the data storage unit and the failed mass storage device is replaced. Because data previously stored on the non-failed mass storage devices of the data storage sled being removed has been copied to other mass storage devices of the data storage unit, the data remains available even while the data storage sled is at least partially removed from the data storage unit.

At 1260, the data storage sled with the replaced mass storage device is re-installed in the data storage unit. At 1262 mass storage devices of the replaced data storage sled are made available for allocation of columns on the mass storage devices of the data storage sled. In some embodiments, data storage space of the non-failed mass storage devices of the data storage sled may be released and made available to store data for newly allocated extents. In some embodiments, the non-failed mass storage devices may still store volume data that has been copied to other mass storage devices in the data storage unit. In some embodiments, the indexes of the respective head nodes may be updated to indicate volume data that is still stored on the non-failed mass storage devices.

Multi-Tier Control Plane

In some embodiments, a data storage system may include multiple data storage units. Management of the data storage system may be performed by a multi-tiered control plane. For example, in some embodiments a zonal control plane may determine which data storage units new volumes are to be allocated to and may perform migration of volumes between data storage units to balance loads. Also, in some embodiments, a local control plane of a data storage unit may determine which head nodes of the data storage unit are to be assigned to a particular volume or volume partition as a primary head node and as reserve head nodes. Also, a local control plane may manage allocation of extents within a data storage unit via a “sandbox” technique and may perform fail over operations in response to a failure of a head node, a mass storage device, or a data storage sled. In some embodiments, a data storage unit may operate autonomously from a zonal control plane subsequent to a volume being assigned to the data storage unit. Because data storage units may operate autonomous from a zonal control plane, a failure of a zonal control plane may not impact a data storage unit's ability to respond to read and write requests or perform fail-over operations in response to a failure of a head node or a mass storage device. Also, because a local control plane of a data storage unit only affects a single data storage unit, a failure of a local control plane may have a blast radius that is limited to a single data storage unit. Furthermore, a data storage unit may implement a local control plane on one or more head nodes of a data storage unit and implement a lease protocol to allow for fail over of the local control plane from one head node to another head node in response to a failure of a head node implementing the local control plane. In some embodiments, a local control plane may utilize a distributed value store that is distributed across the plurality of head nodes of the data storage unit. Thus, when a particular head node implementing a local control plane fails, another head node taking over implementation of the local control plane may utilize the distributed value store without values in the value store being lost due to the failure of the head node previously implementing the local control plane.

FIG. 13A is a block diagram illustrating a process for creating a volume involving a zonal control plane, a local control plane, and head nodes of a data storage system, according to some embodiments. Data storage system 1300 includes one or more computing devices that implement zonal control plane 1304 and also includes data storage units 1306, 1332, and 1334. Data storage units 1306, 1332, and 1334 may be the same as any of the data storage units described in FIGS. 1-12 and 14-23. Data storage unit 1306 includes head nodes 1308, 1312, 1314, and 1316 and data storage sleds 1318. A local control plane 1310 is implemented on head node 1308. Data storage unit 1332 includes head nodes 1320, 1322, 1326, and 1328 and data storage sleds 1330. A local control plane 1324 for data storage unit 1332 is implemented on head node 1322. Data storage unit 1334 includes head nodes 1336, 1338, 1340, and 1344 and sleds 1346. A local control plane 1342 for data storage unit 1334 is implemented on head node 1340. As can be seen a local control plane for a data storage unit can be implemented on any one or more head nodes of a plurality of head nodes of a data storage unit. In some embodiments, a local control plane may be logically separated from a data plane of a head node, for example a local control plane may be located in a separate container. In some embodiments, each head node of a data storage unit may include logically isolated program instructions for implementing a local control plane and a portion of a distributed value store distributed across logically isolated portions of respective ones of the head nodes. In such embodiments, a given head node holding a lease for implementing the local control plane may implement the local control plane using the program instructions stored in the given head node. Upon failure of the given head node, another given head node may assume the lease for implementing the local control plane and may implement the local control plane using the program instructions for implementing the local control plane stored in the other given head node. For example, the given head node and the other given head node may both store program instructions for implementing the local control plane and a single one of the given head node or the other given head node may implement the local control plane at a given time.

Client device(s) 1302 may be part of a separate network that is separate from data storage system 1300, such as a customer network, or may be client devices within a provider network that utilizes data storage system 1300. Client device(s) 1302 send volume request A 1348 and volume request B 1350 to zonal control plane 1304 to request volumes of data storage system 1300 be allocated to the client devices. In response, zonal control plane 1304 issues a volume creation instruction A 1352 to data storage unit 1306 and a volume creation instruction B 1358 to data storage unit 1332. In some embodiments, volume creation instructions from a zonal control plane may be processed by a local control plane of a data storage unit. For example, local control plane 1310 of data storage unit 1306 processes volume creation instruction A 1352 and local control plane 1324 of data storage unit 1332 processes volume creation instruction B 1358. In some embodiments, a zonal control plane may receive accumulated performance and usage metrics from data storage units and assign volumes, based on the accumulated performance and usage metrics. For example, a zonal control plane may attempt to balance loads between data storage units by selecting to assign new volumes to data storage units that have accumulated performance and usage metrics that indicate less load than other data storage units.

In order to process a volume creation instruction, a local control plane may assign a head node of a data storage unit to function as a primary head node for a volume and may assign two or more other head nodes of a data storage unit to function as reserve head nodes for the volume. For example, local control plane 1310 assigns head node 1312 as a primary head node for the newly created volume via assignment 1354 and assigns head nodes 1314 and 1316 as reserve head nodes for the volume via assignments 1356. Also, local control plane 1324 of data storage unit 1332 assigns head node 1320 as a primary head node for a newly created volume via assignment 1360 and assigns head nodes 1326 and 1328 as reserve head nodes for the volume via assignments 1362. As can be seen, any one of the head nodes of a data storage unit may be selected to function as a primary or reserve head node for a given volume or volume partition. Also, a local control plane of a data storage unit may collect performance information from head nodes and select primary and reserve head nodes for a given volume based on a current loading of head nodes in a data storage unit. In some embodiments, a local control plane may attempt to balance loads between head nodes when assigning primary and reserve head nodes for a given volume.

FIG. 9B is a block diagram illustrating head nodes of a data storage unit servicing read and write requests independent of a zonal control plane of a data storage system, according to some embodiments. Data storage system 1300 illustrated in FIG. 13B is the same data storage system 1300 as illustrated in FIG. 13A and shows read and write requests being sent to head nodes after primary and reserve head nodes for the newly created volumes have been assigned. As can be seen, read and write requests may be serviced by data storage units of a data storage system independent of a zonal control plane. Also, in some embodiments, read and write requests may be serviced independent of a local control plane. For example read request 1368 and write request 1364 are directed directly to head node 1312 that functions as a primary head node for the newly created volume. Also, primary head node sends read data 1370 and write acknowledgement 1366 to client device(s) 1302 without passing the read data 1370 or the write acknowledgment 1366 through zonal control plane 1304 or local control plane 1310. In some embodiments, each head node may be assigned at least one public network address, such as a public IP address. When a head node is assigned to function as a primary head node for a volume of a client, the primary head node's public IP address may be communicated to the client device and the client device's address may be communicated to the head node functioning as primary head node. Thus, subsequent communications between the head node and the client device may be directly routed between the exchanged address information. In some embodiments, read and write requests may be directed to both a primary and reserve head nodes. For example, if a client does not receive a response from a primary head node, the client may direct a read or write request to a reserve head node. In some embodiments, this may trigger a reserve head node to attempt to assume the role of primary head node.

FIG. 14A is a block diagram of a head node, according to some embodiments. Head node 1400 may be any of the head nodes described in FIG. 1-13 or 15-23. Head node 1400 includes a data control plane 1402, storage 1410, local control plane 1404, and monitoring module 1416. A data control plane of a head node, such as data control plane 1402, may service read and write requests directed to the head node. For example, a data control plane may store one or more public IP addresses of the head node and provide the public IP addresses of the head node to client devices to allow the client devices to communicate with the head node. A storage of a head node, such as storage 1410, may include a log, such as log 1412, and an index, such as index 1414. Log 1412 and index 1414 may be similar to log 408 and index 406 as described in regard to FIGS. 4A and 4B and may store pointers for volume data indicating where the volume data is stored. In some embodiments, a data control plane, such as data control plane 1402, may consult an index, such as index 1414, in order to service read and write requests directed at a particular volume for which the head node is functioning as a primary head node. In some embodiments, an index, such as index 1414 may indicate whether a portion of volume data for a volume is stored in a log of the head node, such as log 1412, or is stored in an extent across multiple data storage sleds, such as mass storage devices 1422 of data storage sled 1418 illustrated in FIG. 14B that also includes sled controller 1420. In addition, a head node may include program instructions for implementing a local control plane that are logically isolated from the data control plane of the head node.

In some embodiments, a local control plane includes an extent allocation service, such as extent allocation service 1406, and a distributed value store, such as value store 1408. An extent allocation service may provide “sandbox” recommendations to head nodes of a data storage unit that include sets of columns from which the head nodes may select new extents. A value store may store extent allocation information and may also store head node assignment information. In some embodiments, a local control plane may provide sequence numbers to newly assigned primary head nodes. In some embodiments, a distributed value store, such as value store 1408, may be implemented over all or a portion of the head nodes of a data storage unit. This may provide fault tolerance such that if any one or more of the head nodes fail, the remaining head nodes may include data from the distributed data store, such that data from the distributed data store is not lost due to the failure of the one or more head nodes.

In some embodiments, a head node includes a monitoring module, such as monitoring module 1416. Monitoring module may collect performance and/or usage metrics for the head node. A head node, such as head node 1400 may provide performance and/or usage metrics to a local control plane, such as local control plane 1404, or may provide performance and/or usage metrics to a zonal control plane.

FIG. 15 is a high-level flowchart illustrating a process of creating a volume in a data storage system, according to some embodiments.

At 1502, a local control plane of a data storage unit of a data storage system receives a volume assignment from a zonal control plane of the data storage system.

At 1504, the local control plane assigns a first head node of the data storage unit to function as a primary head node for the newly created or newly assigned volume. At 1506, the local control plane assigns two or more other head nodes of the data storage unit to function as a reserve head nodes for the newly created or newly assigned volume. Note that in some embodiments, a zonal control plane may move volume between data storage units of a data storage system. Thus the newly assigned volume may be an existing volume being moved from another data storage unit of the data storage system. Also, a local control plane of a data storage unit may select head nodes to function as primary and reserve head nodes from any of the head nodes of the data storage unit. However, a head node functioning as a primary head node may not function as a reserve head node for the same volume. But, a given head node may function as a primary head node for more than one volume and may also function as a reserve head node for one or more other volumes.

At 1508 the primary head node for the volume services read and write requests directed at the volume. In some embodiments, a head node functioning as a primary head node may service read and write requests independent of a zonal control plane and/or independent of a local control plane of a data storage unit.

FIG. 16A is a high-level flowchart illustrating a local control plane of a data storage unit providing storage recommendations to a head node of the data storage unit for locations to store data in data storage sleds of the data storage unit for a given volume, according to some embodiments.

At 1602, a local control plane of a data storage unit allocates a “sandbox” to a particular volume serviced by a primary head node functioning as primary head node for the particular volume. The sandbox may include a set of columns of mass storage devices from which the head node is recommended to select extents for the particular volume. In some embodiments, the sandbox may include extents that already include corresponding columns in multiple mass storage devices and the head node may be recommended to select extents for the particular volume from the extents included in the sandbox recommendation.

At 1604, the local control plane collects performance metrics from data storage sleds and/or head nodes in the data storage unit.

At 1606, the local control plane issues “sandbox” updates to the primary head node functioning as a primary head node for the particular volume. The sandbox updates may be based on the collected performance metrics collected at 1604. A local control plane may allocate sandbox recommendations and update sandbox recommendations to avoid heat collisions wherein multiple head nodes are attempting to access the same data storage sleds at the same time. In some embodiments, a sandbox recommendation may be a loose constraint and a head node functioning as a primary head node may select columns or extents that are not included in a sandbox recommendation. It should also be noted that sandbox recommendation and performance and/or usage metrics collection may be performed outside of the I/O path. Thus, if there is a failure or corruption of the local control plane, reads and writes may continue to be processed by non-affected head nodes of a data storage unit. Also, a sandbox allocated to a particular volume may remain with the particular volume during a failover of head nodes. For example, if a primary head node for a particular volume fails, the sandbox allocated for the particular volume may move with the particular volume that will now be serviced by a former reserve head node. Subsequent to a head node failover, sandbox updates, such as the sandbox updates described at 1606, may be issued from the local control plane to the new primary head node for the volume.

FIG. 16B is a high-level flowchart illustrating a head node of a data storage unit storing data in data storage sleds of the data storage unit, according to some embodiments.

At 1652, a primary head node determines a segment of data to be flushed to mass storage devices in data storage sleds of a data storage unit. For example, exceeding one or more thresholds, such as an amount of data stored in a log, an age of data stored in a log, or an infrequency at which the data is accessed in a log, may trigger a primary head node to flush data to data storage sleds.

At 1654, a primary head node may determine if there is available space in a sandbox allocated to a volume serviced by the primary head node. At 1656, in response to determining there is sufficient space in the sandbox, the primary head node flushes the data to extents that include columns in the allocated sandbox allocated for the volume. At 1658, in response to determining there is insufficient space in the sandbox or in response to determining a placement in the sandbox will violate a placement restriction, such as a durability level, the primary head node selects extents outside of the sand box.

FIG. 17 is a high-level flowchart illustrating head nodes of a data storage unit performing a fail over operation in response to a failure of or loss of communication with one of the head nodes of the data storage unit, according to some embodiments.

At 1702 communication with a primary head node is lost or the primary head node fails. In some embodiments, a client device may lose contact with a primary head node and the client device may contact one of the reserve head nodes. This may trigger the reserve head node to attempt to take over as primary head node.

At 1704, in response to one of the reserve head nodes attempting to take over as primary head node, the local control plane issues a new sequence number to the reserve head node. The new sequence number may be greater than a sequence number previously issued to the previous primary head node. The local control plane may also issue the new sequence number to a remaining reserve head node of a set of two or more reserve head nodes. In some embodiments, the local control plant may initiate the fail-over in response to an indication of a failed head node from a head node failure detection agent, such as head node failure detection agent 1054 described in FIG. 10. The new sequence number may be used by the reserve head node that is being promoted to primary head node to gain write access to extents that were previously reserved for write access only by the previous primary head node.

At 1706, the reserve head node being promoted to primary head node assumes the role of primary head node and begins to service writes directed to the volume. In some embodiments, the reserve head node being promoted to primary head node may assume the role of primary head node by presenting the new sequence number received from the local control plane to a remaining reserve head node and sled controllers of the data storage system and receiving, from the sled controllers, credentials for writing to columns that store data of the volume.

At 1708, the local control plane designates another head node of the data storage unit to function as a replacement reserve head node for the volume or volume partition. Note that one of the previous reserve head nodes has assumed the role of primary head node, such that the volume is without a set of two or more reserve head nodes causing the local control plane to designate a new replacement reserve head node.

At 1710, the new primary head node (previous reserve head node) replicates log and index data for the volume to the newly designated replacement reserve head node. In some embodiments, replicating log and index data may include replicating index data for the volume including pointers for volume data stored in data storage sleds of a data storage unit and volume data stored in the log of the new primary head node (previous reserve head node) that has not yet been flushed to the data storage sleds.

FIG. 18 is a block diagram illustrating performance and/or usage metrics being collected and accumulated in a data storage unit, according to some embodiments.

Data storage system 1800 may be the same as data storage system 1300 illustrated in FIG. 13A-13B. Data storage system includes zonal control plane 1804 and data storage units 1806, 1828, and 1830. In some embodiments, data storage sleds and head nodes of a data storage unit may report performance and usage metrics to a local control plane for the data storage unit. For example, head nodes 1808, 1812, and 1814 of data storage unit 1806 report performance and usage metrics to local control plane 1810 of data storage unit 1806. Also, a sled controller of each of data storage sleds 1816 may report performance and usage metrics to local control plane 1810. In a similar manner, data storage sleds 1826 and head nodes 1818, 1820, and 1824 of data storage unit 1828 may report performance and usage metrics to local control plane 1822 of data storage unit 1828. Likewise, data storage sleds 1840 and head nodes 1832, 1834, and 1836 of data storage unit 1830 may report performance and usage metrics to local control plane 1838. In some embodiments, each local control plane of a data storage unit may in turn report accumulated performance and usage metrics to a zonal control plane for the data storage system. For example, local control planes 1810, 1822, and 1838 report performance and usage metrics to zonal control plane 1804. In some embodiments local control planes may use performance and usage metrics to balance loads between head nodes and to update sandbox recommendations that indicate recommended data storage sleds from which head nodes should select extents for a given volume. Also, a zonal control plane may use cumulative performance and usage metrics to balance volume assignments and/or move volumes between data storage units. In some embodiments, performance and usage metrics may be used by a local control plane to balance loads within a given data storage unit and accumulated performance and usage metrics may be used by a zonal control plane to balance loads between data storage units.

In some embodiments, a head node failure detection agent, such as head node failure detection agent 1054 described in FIG. 10, may piggy-back on the reporting of performance and usage metrics. For example, a head node failure detection agent may monitor head nodes for reporting of performance and usage metrics and may identify a failed head node by the failure to report performance and usage metrics without sending a ping to the head nodes.

Input/Output Fencing of Mass Storage Devices from Unauthorized Head Nodes

In some embodiments, a sled controller of a data storage sled may implement a fencing protocol that prevents unauthorized head nodes from writing data to columns of mass storage devices located in a data storage sled along with the sled controller. In some embodiments, a sled controller may issue credentials or tokens to head nodes for accessing columns allocated to a particular volume serviced by the respective head nodes. The sled controller may only issue a new token to a head node if a column associated with the credential or token is not currently reserved or if a head node seeking to access the column presents a sequence number greater than a sequence number stored for the column that indicates a sequence number of a previous head node that requested to access the column. For example, a newly designated primary head node for a given volume may receive from a local or zonal control plane a sequence number for the given volume that is greater than a previously issued sequence number for the given volume. The newly designated primary head node may then present the new sequence number to sled controllers of data storage sleds that include columns allocated for the volume. The sequence number of the newly designated primary head node may be greater than a sequence number stored in the columns that corresponded to a sequence number of a previous primary head node that accessed the columns. Upon determining that the newly designated primary head node has presented a sequence number greater than a stored sequence number, the sled controllers may issue a new token to the newly designated primary head node for accessing the columns.

For example, FIG. 19 illustrates interactions between a local control plane, head nodes, and data storage sleds of a data storage unit in relation to writing data to mass storage devices of a data storage sled of the data storage unit, according to some embodiments. Various interactions are illustrated between local control plane 1902 of data storage unit, head nodes 1904 and 1906 of the data storage unit and sled controllers 1908 of the data storage unit. Any of the data storage units described herein may include a local control plane, head nodes and sled controllers of data storage sleds that function as described in FIG. 19.

Phases 1, 2, and 3 are illustrated to show interactions that take place at different phases of operation of a data storage system. For example, phase 1 may be a normal phase in which a head node is assuming the role of primary head node for a volume or volume partition and functioning as the primary head node for the volume or volume partition. Phase 2 may represent a failover phase in which a reserve head node is assuming the role of primary head node for the volume, and phase 3 may represent a new normal phase wherein a newly designated primary head node is functioning as a primary head node for the volume.

At phase 1, local control plane 1902 assigns (1910) head node 1904 to be a primary head node for a volume and assigns (1912) head node 1906 to be a reserve head node for the volume (while not shown, the local control plane also assigns an additional head node to be a second reserve head node for the volume). Assignment 1910 may include a new sequence number that is a monotonically increasing number that is greater than all sequence numbers previously issued by the local control plane 1902. At phase 1, in order to reserve columns of mass storage devices in different ones of multiple data storage sleds of a data storage unit, head node 1904 presents (1914) the new sequence number to sled controllers 1908 and reserves (1914) columns on mass storage devices located in data storage sleds that include the sled controllers 1908. At 1916, the sled controllers issue credentials or tokens to head node 1904 indicating that the columns are reserved for the volume and that head node 1904 is functioning as primary head node for the volume. At 1918, head node 1904 then issues a write request to sled controllers 1908 and includes along with the write requests the tokens or credentials issued by the sled controllers. The sled controllers verify that the credentials or tokens included with the write request are valid, perform the requested write, and at 1920 issue a write acknowledgement to head node 1904. Also the sled controllers store the sequence number and volume ID or volume partition ID in each column along with the data included with the write request.

During phase 2 or the fail over phase, communication is lost with head node 1904 at 1922. In some embodiments, loss of communication with a primary head node may be triggered by a client device failing to be able to reach the primary head node and instead contacting the reserve head node. In such embodiments, the reserve head node may attempt to take over as primary head node (not illustrated in FIG. 19). In some embodiments, a local control plane may determine that a primary head node has been lost. In response to determining that a primary head node has failed or there is a loss of communication with a primary head node, at 1924, local control plane 1902 promotes head node 1906 to primary head node for the volume and issues a new sequence number to head node 1906. Head node 1906 then, at 1926, presents the new sequence number issued to head node 1906 to sled controllers 1908 and requests access to the columns that store data for the volume for which head node 1906 is now the primary head node. The new sequence number issued to head node 1906 is greater than the sequence number issued to head node 1904 at 1910. At 1928, the sled controllers issue a new token or credential to head node 1906 that supersedes the token or credential issued to head node 1904 at 1916.

During phase 3, head node 1906 functions as a primary head node for the volume. At 1930 head node 1906 includes with subsequent write requests the tokens issued from the sled controllers at 1928. At 1932 sled controllers acknowledge subsequent writes from head node 1906. Also, at 1934 head node 1904 that has lost communication with control plane 1902 and/or head node 1906 attempts to perform a write to columns assigned to the volume. However, subsequent to the failover, head node 1904 is no longer the primary head node for the volume and head node 1906 is functioning as primary head node for the volume. Thus, head node 1906 has exclusive access to columns of mass storage devices of extents allocated to the volume. Thus, at 1934 when head node 1904 attempts to access the columns sled controllers 1908 decline (1936) to perform the write. In addition, at 1936 the head node 1904 may read the volume ID and new sequence number stored in the columns assigned to the volume. The columns may store the new sequence number issued to head node 1906 during the failover. Upon determining that a new sequence number has been stored that supersedes the sequence number last issued to head node 1904, head node 1904 may determine that it is no longer primary head node for the volume and may assume a role of reserve head node for the volume.

Note that each column stores a volume or volume partition ID for a volume for which the column is allocated along with a most recent sequence number. The volume ID and sequence number may be saved in persistent memory of the column. Also, a sled controller may store volume ID and sequence number information in a volatile memory of the sled controller. However, when a sled controller is reset, e.g. loses power, the volume and sequence number stored in the sled controller may be lost. However, volume and sequence number information stored in columns of mass storage devices may be persisted. This avoids complications that may arise if mass storage devices are moved between data storage sleds. For example, if a mass storage device is moved within a data storage sled or amongst data storage sleds, sled controller volume ID and sequence number information may become inaccurate. However, because volume ID and sequence number information is lost from a sled controller whenever power is lost to the sled controller, the sled controller may be reset when a sled is removed from a data storage unit to access mass storage devices in the data storage sled avoiding such complications. Thus, subsequent to a reboot of a sled controller, head nodes serving as primary head nodes for volumes that have columns allocated on a sled that includes the sled controller may need to reclaim the columns. For example the head nodes may present respective sequence numbers issued to the head nodes and the sled controllers may issue new credentials or tokens to the head nodes if the sequence numbers presented have not be superseded, e.g. the sequence numbers stored in the columns are not greater than the sequence numbers being presented by the head nodes.

FIG. 20 is a high-level flowchart of a head node of a data storage unit flushing data stored in a storage of the head node to a data storage sled of the data storage unit, according to some embodiments.

At 2002, a head node functioning as a primary head node for a volume receives a write request. At 2004, the head node writes data included with the write request to a storage of the head node, such as a log of the head node.

At 2006, in response to determining data stored in the storage of the head node exceeds a threshold, the head node requests sled controllers of multiple data storage sleds cause portions of the data stored in the storage of the head node be stored in multiple portions of different mass storage devices in different ones of the data storage sleds of the data storage unit. Requesting the sled controllers to store the data may further include presenting credentials (2008), such as credentials described in FIG. 19, to each of the sled controllers.

FIG. 21 is a high-level flowchart of a sled controller of a data storage sled processing a write request, according to some embodiments.

At 2102, a sled controller receives a credential from a head node along with a write request. At 2104 and 2106, the sled controller determines if the credential received at 2102 is a currently valid credential for a column of a mass storage device in a data storage sled that includes the sled controller. A sled controller may compare a sequence number and/or volume ID included in the credential with a sequence number and/or volume ID saved in the column for which access is requested. If the sequence number and/or volume ID included in the credential match the sequence number and/or volume ID stored in the column the sled controller may determine that the credential is valid. In some embodiments, a sled controller may store information that corresponds with a token or credential, such as a token number. If the information that corresponds with the token stored by the sled controller matches information included in the token, the sled controller may determine the credential or token is a valid credential. If a sequence number included in the credential or token is inferior to a sequence number stored in the column, the sled controller may determine that the credential or token is invalid. In some embodiments, a head node may not currently have credentials for a particular column and may present a sequence number that is greater than a stored sequence number stored for the column and the sled controller may issue credentials that supersede all previously issued credentials for the column, such as a new token that supersedes all tokens previously issued for the column.

At 2112, in response to determining at 2106 that the credential included with the write request is an invalid credential, the sled controller does not perform the requested write and returns a message to the head node indicating that the credential is invalid.

At 2108, in response to determining the credential is valid, the sled controller performs the requested write to the requested column of a mass storage device in the data storage sled along with the sled controller. At 2110 the sled controller acknowledges the write has been performed to the head node.

Data Storage Unit Design with Redundant Networks and Redundant Power

In some embodiments, a data storage unit may include redundant network and redundant power supplies and power distribution systems. Such redundant systems may reduce probabilities of failure thus allowing, for example, a single rack to store all parts of a volume while still meeting customer requirements for reliability and data durability. However, in some embodiments, a volume or volume partition may be stored in more than one data storage unit.

FIGS. 22A-D illustrate a data storage unit with redundant network paths within the data storage unit, according to some embodiments. Data storage unit 2250 illustrated in FIGS. 22A-D may be the same as data storage unit 100 illustrated in FIG. 1, or any other data storage unit described herein. FIGS. 22A-D further illustrate communication paths between network switches 2202 and 2204, head nodes 2206-2208, and data storage sleds 2234-2244. As can be seen, at least two redundant networks, including internal network 2252 and internal network 2254, are implemented within data storage unit 2250. Note that paths between components of data storage unit 2250 are illustrated on either side of data storage unit 2250 for clarity, but in practice paths between components of a data storage unit may be within the data storage unit over wires, cables, busways, etc. of the data storage unit.

In FIG. 22A redundant communication paths are established between head node 2206 and network 2228 via network switches 2202 and 2204. In some embodiments, a head node, such as head node 2206, may be assigned redundant network addresses routable from devices external to data storage unit 2250, such as public IP addresses, and may be reachable via either one of the network address using either one of network switches 2202 and 2204.

FIG. 22B illustrates redundant network paths between head nodes. For example head node 2206 may reach head node 2208 via internal network 2252 or internal network 2254, wherein internal network 2252 is via network switch 2202 and internal network 2254 is via network switch 2204. Note that there is a single network hop between head node 2206 and head node 2208 via network switch 2202 or network switch 2204. In some embodiments, a data storage unit may have a single network hop between head nodes and data storage sleds so that input/output operations do not require multiple network hops to retrieve or write data, thus improving IOPS performance and latency.

FIG. 22C illustrates redundant network paths between head nodes and data storage sleds. For example, head node 2206 may reach any of data storage sleds 2234-2244 via sled controllers 2212-2222. Each sled controller may include two network ports that each are connected to different ones of internal networks 2252 or 2254 via either one or network switches 2202 or 2204. In some embodiments, each head node may be assigned at least two private network addresses and each sled controller may be assigned at least two private network addresses. The private network addresses assigned to the head nodes and sled controllers of the data storage sleds may enable the head nodes and sled controllers to communicate with each other via either one of internal networks 2252 or 2254. FIG. 22D illustrates a head node sending a response communication to a client device via either one of internal networks 2252 or 2254.

In some embodiments, a data storage unit may be configured to accept more or less head nodes in a rack of the data storage unit or to accept more or less data storage sleds in the rack of the data storage unit. Thus, compute capacity and data storage capacity of a data storage unit may be adjusted by varying a quantity of head nodes and/or data storage sleds that are included in the data storage unit.

FIGS. 23A-C illustrate a data storage unit configured to allow scaling of storage capacity and processing capacity, according to some embodiments. For example, data storage unit 2302 is shown in arrangement 2300 in FIG. 23A and in arrangement 2320 in FIG. 23B. In arrangement 2320 data storage unit 2302 includes more data storage sleds than in arrangement 2300. Also, in arrangement 2340, data storage unit 2302 includes more head nodes than in arrangement 2300. In some embodiments, a ratio of head nodes to data storage sleds may be adjusted to meet customer needs.

Example Computer System

FIG. 24 is a block diagram illustrating an example computer system, according to various embodiments. For example, computer system 2400 may be configured to implement storage and/or head nodes of a data storage unit, storage and/or a sled controller of a data storage sled, other data stores, and/or a client, in different embodiments. Computer system 2400 may be any of various types of devices, including, but not limited to, a personal computer system, desktop computer, laptop or notebook computer, mainframe computer system, handheld computer, workstation, network computer, a consumer device, application server, storage device, telephone, mobile telephone, or in general any type of computing device.

Computer system 2400 includes one or more processors 2410 (any of which may include multiple cores, which may be single or multi-threaded) coupled to a system memory 2420 via an input/output (I/O) interface 2430. Computer system 2400 further includes a network interface 2440 coupled to I/O interface 2430. In various embodiments, computer system 2400 may be a uniprocessor system including one processor 2410, or a multiprocessor system including several processors 2410 (e.g., two, four, eight, or another suitable number). Processors 2410 may be any suitable processors capable of executing instructions. For example, in various embodiments, processors 2410 may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, each of processors 2410 may commonly, but not necessarily, implement the same ISA. The computer system 2400 also includes one or more network communication devices (e.g., network interface 2440) for communicating with other systems and/or components over a communications network (e.g. Internet, LAN, etc.).

In the illustrated embodiment, computer system 2400 also includes one or more persistent storage devices 2460 and/or one or more I/O devices 2480. In various embodiments, persistent storage devices 2460 may correspond to disk drives, tape drives, solid state memory, other mass storage devices, block-based storage devices, or any other persistent storage device. Computer system 2400 (or a distributed application or operating system operating thereon) may store instructions and/or data in persistent storage devices 2460, as desired, and may retrieve the stored instruction and/or data as needed. For example, in some embodiments, computer system 2400 may host a storage unit head node, and persistent storage 2460 may include the SSDs that include extents allocated to that head node.

Computer system 2400 includes one or more system memories 2420 that are configured to store instructions and data accessible by processor(s) 2410. In various embodiments, system memories 2420 may be implemented using any suitable memory technology, (e.g., one or more of cache, static random access memory (SRAM), DRAM, RDRAM, EDO RAM, DDR 10 RAM, synchronous dynamic RAM (SDRAM), Rambus RAM, EEPROM, non-volatile/Flash-type memory, or any other type of memory). System memory 2420 may contain program instructions 2425 that are executable by processor(s) 2410 to implement the methods and techniques described herein. In various embodiments, program instructions 2425 may be encoded in platform native binary, any interpreted language such as Java™ byte-code, or in any other language such as C/C++, Java™, etc., or in any combination thereof. For example, in the illustrated embodiment, program instructions 2425 include program instructions executable to implement the functionality of a storage node, in different embodiments. In some embodiments, program instructions 2425 may implement multiple separate clients, nodes, and/or other components.

In some embodiments, program instructions 2425 may include instructions executable to implement an operating system (not shown), which may be any of various operating systems, such as UNIX, LINUX, Solaris™, MacOS™, Windows™, etc. Any or all of program instructions 2425 may be provided as a computer program product, or software, that may include a non-transitory computer-readable storage medium having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to various embodiments. A non-transitory computer-readable storage medium may include any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). Generally speaking, a non-transitory computer-accessible medium may include computer-readable storage media or memory media such as magnetic or optical media, e.g., disk or DVD/CD-ROM coupled to computer system 2400 via I/O interface 2430. A non-transitory computer-readable storage medium may also include any volatile or non-volatile media such as RAM (e.g. SDRAM, DDR SDRAM, RDRAM, SRAM, etc.), ROM, etc., that may be included in some embodiments of computer system 2400 as system memory 2420 or another type of memory. In other embodiments, program instructions may be communicated using optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.) conveyed via a communication medium such as a network and/or a wireless link, such as may be implemented via network interface 2440.

In some embodiments, system memory 2420 may include data store 2445, which may be configured as described herein. In general, system memory 2420 (e.g., data store 2445 within system memory 2420), persistent storage 2460, and/or remote storage 2470 may store data blocks, replicas of data blocks, metadata associated with data blocks and/or their state, configuration information, and/or any other information usable in implementing the methods and techniques described herein.

In one embodiment, I/O interface 2430 may be configured to coordinate I/O traffic between processor 2410, system memory 2420 and any peripheral devices in the system, including through network interface 2440 or other peripheral interfaces. In some embodiments, I/O interface 2430 may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 2420) into a format suitable for use by another component (e.g., processor 2410). In some embodiments, I/O interface 2430 may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface 2430 may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments, some or all of the functionality of I/O interface 2430, such as an interface to system memory 2420, may be incorporated directly into processor 2410.

Network interface 2440 may be configured to allow data to be exchanged between computer system 2400 and other devices attached to a network, such as other computer systems 2490, for example. In addition, network interface 2440 may be configured to allow communication between computer system 2400 and various I/O devices 2450 and/or remote storage 2470. Input/output devices 2450 may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or retrieving data by one or more computer systems 2400. Multiple input/output devices 2450 may be present in computer system 2400 or may be distributed on various nodes of a distributed system that includes computer system 2400. In some embodiments, similar input/output devices may be separate from computer system 2400 and may interact with one or more nodes of a distributed system that includes computer system 2400 through a wired or wireless connection, such as over network interface 2440. Network interface 2440 may commonly support one or more wireless networking protocols (e.g., Wi-Fi/IEEE 802.11, or another wireless networking standard). However, in various embodiments, network interface 2440 may support communication via any suitable wired or wireless general data networks, such as other types of Ethernet networks, for example. Additionally, network interface 2440 may support communication via telecommunications/telephony networks such as analog voice networks or digital fiber communications networks, via storage area networks such as Ethernet, Fibre Channel SANs, or via any other suitable type of network and/or protocol. In various embodiments, computer system 2400 may include more, fewer, or different components than those illustrated in FIG. 24 (e.g., displays, video cards, audio cards, peripheral devices, other network interfaces such as an ATM interface, an Ethernet interface, a Frame Relay interface, etc.)

It is noted that any of the distributed system embodiments described herein, or any of their components, may be implemented as one or more network-based services. For example, a compute cluster within a computing service may present computing and/or storage services and/or other types of services that employ the distributed computing systems described herein to clients as network-based services. In some embodiments, a network-based service may be implemented by a software and/or hardware system designed to support interoperable machine-to-machine interaction over a network. A network-based service may have an interface described in a machine-processable format, such as the Web Services Description Language (WSDL). Other systems may interact with the network-based service in a manner prescribed by the description of the network-based service's interface. For example, the network-based service may define various operations that other systems may invoke, and may define a particular application programming interface (API) to which other systems may be expected to conform when requesting the various operations. though

In various embodiments, a network-based service may be requested or invoked through the use of a message that includes parameters and/or data associated with the network-based services request. Such a message may be formatted according to a particular markup language such as Extensible Markup Language (XML), and/or may be encapsulated using a protocol such as Simple Object Access Protocol (SOAP). To perform a network-based services request, a network-based services client may assemble a message including the request and convey the message to an addressable endpoint (e.g., a Uniform Resource Locator (URL)) corresponding to the network-based service, using an Internet-based application layer transfer protocol such as Hypertext Transfer Protocol (HTTP).

In some embodiments, network-based services may be implemented using Representational State Transfer (“RESTful”) techniques rather than message-based techniques. For example, a network-based service implemented according to a RESTful technique may be invoked through parameters included within an HTTP method such as PUT, GET, or DELETE, rather than encapsulated within a SOAP message.

Although the embodiments above have been described in considerable detail, numerous variations and modifications may be made as would become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such modifications and changes and, accordingly, the above description to be regarded in an illustrative rather than a restrictive sense. 

What is claimed is:
 1. A method, comprising: receiving a write request for a volume partition, by a head node of a data storage system acting as a primary head node for the volume partition; writing, by the head node, data included in the write request to a storage of the head node; causing, by the head node, the data included with the write request to be replicated from the head node to a set of two or more other head nodes of the data storage system acting as reserve head nodes for the volume partition; receiving, by the head node, a plurality of additional write requests for the volume partition and performing, for the additional write requests, said writing data included in the additional write requests to the storage of the head node and said causing data included in the additional write requests to be replicated to the set of two or more head nodes; providing an acknowledgement of the write request subsequent to the data being replicated to the two or more reserve head nodes; and erasure encoding respective parts of the data included in the write request and the additional write requests that is stored in the storage of the head node and causing the erasure encoded respective parts of the data to be stored in a plurality of mass storage devices of the data storage system, wherein the acknowledgement is provided asynchronously with respect to the respective parts of the data being erasure encoded.
 2. The method of claim 1, comprising: measuring write latencies of the set of two or more head nodes acting as the reserve head nodes for the volume partition; and in response to a write latency for one of the set of two or more head nodes exceeding a first write latency threshold: reducing a membership of the reserve head nodes required to acknowledge replication of write data to the head node acting as the primary head node before acknowledging the write request to a client of the data storage system.
 3. The method of claim 1, comprising: in response to a write latency for the one of the set of two or more head nodes exceeding a second write latency threshold or a time threshold in a reduce membership state: designating an additional head node of the data storage system as a replacement reserve head node for the volume partition; and initiating a re-mirroring operation to re-mirror volume partition data to the replacement reserve head node.
 4. The method of claim 1, wherein erasure encoding the respective parts of the data comprises: generating striped columns of the data stored in the head node acting as the primary head node for the volume partition; and generating parity columns of the data stored in the head node acting as the primary head node for the volume partition, wherein the striped columns and parity columns comprise fewer copies of the data for the volume partition than are stored in the head node acting as the primary head node for the volume partition and the set of two or more head nodes acting as the reserve head nodes for the volume partition.
 5. The method of claim 4, further comprising: receiving, by the head node acting as the primary head node for the volume partition, an indication that the head node has been designated as a replacement reserve head node for another volume partition; and replicating data stored in a storage of a remaining primary head node for the other volume partition to the storage of the head node.
 6. The method of claim 1, further comprising: receiving an indication of one or more durability requirements for the volume partition from a client of the data storage system; and adjusting a number of reserve head nodes included in the set of two or more reserve head nodes to which write data is replicated based at least in part on the received one or more durability requirements for the volume partition.
 7. A data storage system, comprising: a head node of the data storage system; wherein, based, at least in part, on receiving a write request for a volume partition, the head node, when acting as a primary head node of the data storage system for the volume partition, is configured to: write data included in the write request to a storage of the head node; cause the data included with the write request to be replicated from the head node to a set of two or more other head nodes of the data storage system, wherein the two or more other head nodes are acting as reserve head nodes for the volume partition; wherein the head node, when acting as the primary head node of the data storage system for the volume partition, is further configured to: erasure encode respective parts of the data stored in the storage of the head node for the volume partition and cause the erasure encoded respective parts of the data to be stored in a plurality of respective mass storage devices of the data storage system; and provide an acknowledgement of the write request subsequent to the data being replicated to the two or more reserve head nodes, wherein the head node is configured to provide the acknowledgement prior to the respective parts of the data being erasure encoded.
 8. The data storage system of claim 7, wherein for another volume partition stored in the data storage system, the head node is configured to: receive an indication that the head node has been designated as a replacement reserve head node for the other volume partition; and replicate data stored in a storage of a remaining primary head node for the other volume partition to the storage of the head node.
 9. The data storage system of claim 7, wherein the head node is configured to implement, at least in part, a control plane for the data storage system, wherein the control plane is configured to: measure write latencies with respect to the two or more other head nodes acting as reserve head nodes for the volume partition; and in response to a write latency for one of the reserve head nodes exceeding a write latency threshold: designate an additional head node of the data storage system as a replacement head node for the head node with the write latency that exceeds the write latency threshold; and initiate a re-mirroring operation to re-mirror volume partition data to the replacement head node.
 10. The data storage system of claim 7, wherein the head node is configured to implement, at least in part, a control plane for the data storage system, wherein the control plane is configured to: receive in indication of one or more durability requirements for the volume partition from a client of the data storage service; and adjust a number of reserve head nodes included in the set of two or more reserve head nodes to which write data is replicated.
 11. The data storage system of claim 10, wherein in response to receiving the indication of the one or more durability requirements for the volume, the control plane is also configured to: adjust the erasure encoding such that the number of parts of the data stored in the storage of the head node is stored on more or fewer of the mass storage devices of the data storage system, based, at least in part, on the one or more durability requirements for the volume partition received from the client.
 12. The data storage system of claim 11, wherein the head node is configured to store another volume partition with a lower durability requirement than the volume partition, wherein for the other volume partition, the head node is configured to: write data included in a write request for the other volume partition to a storage of the head node; and cause the data included with the write request for the other volume partition to be replicated from the head node to a set of head nodes comprising fewer head nodes than the set of two or more head nodes to which the data for the volume partition is replicated.
 13. The data storage system of claim 7, wherein the head node is further configured to: receive an indication from a failure detection agent of the data storage system that another head node of the data storage system has failed; identify volume partitions stored on the head node for which primary or reserve replicas are stored on the other head node that has failed; and automatically initiate re-mirroring of replicas for the identified volume partitions from the head node to replacement reserve replicas on respective ones of a plurality of other head nodes of the data storage system.
 14. The data storage system of claim 7, wherein the head node of the data storage system is configured to: receive authorization information from a control plane of the data storage system to act as the primary head node for the volume partition; and include the authorization information with the data to be replicated from the head node to the two or more other head nodes acting as reserve head nodes for the volume partition, wherein the authorization information from the control plane comprises an increasing sequence number that is greater than sequence numbers included in previously issued authorization information.
 15. The data storage system of claim 7, wherein for another volume partition for which the head node is acting as a reserve head node, the head node is configured to: receive data to be replicated to the head node from another head node acting as a primary head node for the other volume partition, wherein the head node receives authorization information from the other head node with the data to be replicated; write the data to be replicated to a storage of the head node if the authorization information has not been superseded by a sequence number previously received by the head node; and decline to write the data to be replicated to the storage of the head node if the authorization information has been superseded by a sequence number previously received by the head node.
 16. The data storage system of claim 15, wherein the head node is configured to implement, at least in part, a control plane for the data storage system, wherein the control plane is configured to: issue new authorization information upon a change in membership of head nodes acting as the primary head node for the volume partition or acting as the reserve head nodes for the volume partition.
 17. A data storage system, comprising: a plurality of head nodes; and a plurality of mass storage devices, wherein for a volume partition of a volume to be stored in the data storage system, a control plane of the data storage system is configured to designate a first head node of the plurality of head nodes as a primary head node for the volume partition and designate two or more other ones of the head nodes of the data storage system as reserve head nodes for the volume partition, wherein, based, at least in part, on receiving a write request for the volume partition, the primary head node for the volume partition is configured to: write data included with the write request to a storage of the primary head node; cause the data included with the write request to be replicated to the two or more reserve head nodes; wherein the primary head node for the volume partition is further configured to: erasure encode respective parts of the data stored in the storage of the primary head node and cause the erasure encoded respective parts of the data to be stored in a plurality of the mass storage devices; and provide an acknowledgement of the write request subsequent to the data being replicated to the two or more reserve head nodes, wherein the head node is configured to provide the acknowledgement prior to the respective parts of the data being erasure encoded.
 18. The data storage system of claim 17, wherein the erasure encoded data stored in the plurality of mass storage devices is stored across more separate mass storage devices than a number of head nodes used to store data for the volume partition, and wherein the erasure encoded data stored in the plurality of mass storage devices comprises fewer copies of data for the volume partition than a number of copies of data for the volume partition stored in the primary head node and the two or more reserve head nodes.
 19. The data storage system of claim 18, wherein the erasure encoded data stored in the plurality of mass storage devices comprises four striped columns of the erasure encoded data and two parity columns of the erasure encoded data, each stored on a different mass storage device of the plurality of mass storage devices of the data storage system.
 20. The data storage system of claim 17, wherein in response to a failure of the primary head node or in response to a failure of one of the reserve head nodes: the control plane of the data storage system is configured to designate a fourth of the plurality of head nodes as a replacement reserve head node for the volume partition.
 21. The data storage system of claim 17, wherein the control plane of the data storage system is further configured to: measure write latencies with respect to the reserve head nodes for the volume partition; and in response to a write latency for one of the reserve head nodes exceeding a write latency threshold: designate an additional head node of the plurality of head nodes as a replacement head node for the head node with the write latency that exceeds the write latency threshold; and initiate a re-mirroring operation to re-mirror volume partition data to the replacement head node. 